Inspect changes in Gitaly fc7f05c95d10184fa76b2e613779bce4e46dd190
Upstream merge commit 329c8cf6ed1d changes Gitaly server version from abb22ce3654f045c0c8b6fec1ba8b7a09eaca5f5 to fc7f05c95d10184fa76b2e613779bce4e46dd190, with changes in protocol or one of the source subtrees currently under watch.
To further inspect, go to an up to date Gitaly source clone and run:
git diff abb22ce3654f045c0c8b6fec1ba8b7a09eaca5f5..fc7f05c95d10184fa76b2e613779bce4e46dd190 -- proto/*.proto internal/backup
Here is a preview, truncated at 500 lines:
diff --git a/proto/log.proto b/proto/log.proto
index 3e8a70799..9b82789a3 100644
--- a/proto/log.proto
+++ b/proto/log.proto
@@ -47,6 +47,13 @@ message LogEntry {
message RepositoryDeletion {
}
+ // AlternateUpdate models an update to the 'objects/info/alternates' file.
+ message AlternateUpdate {
+ // path is the path to set in the alternates file. If the path is empty,
+ // the alternate file is removed.
+ string path = 1;
+ }
+
// relative_path is the relative path of the repository the changes in the
// log entry are targeting.
string relative_path = 1;
@@ -66,6 +73,8 @@ message LogEntry {
RepositoryDeletion repository_deletion = 6;
// repository_creation is set if this log entry creates a repository.
RepositoryCreation repository_creation = 7;
+ // alternate_update records a change to the repository's 'objects/info/alternates' file.
+ AlternateUpdate alternate_update = 8;
}
// LSN serializes a log sequence number. It's used for storing a partition's
A merge request may have already been submitted, check that on the merge commit, as usually changes in Gitaly are not breaking, compliance becoming mandatory in the following development cycles.