Fix comments of GarbageCollectRequest used by gc

Comments for prune field of GarbageCollectRequest indicates that if set
true, dangling objects that are not modified in the last 24 hours would
be dropped. But the time gap is 30 minutes actually.

Commit ab6bc21a1140d0cab98855a7cd7fe81d166a6950 tuned the time gap from
24 hours to 30 minutes, but the proto comments are missed at that time.

Signed-off-by: blanet <moweng.xx@alibaba-inc.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/proto/go/gitalypb/repository-service.pb.go b/proto/go/gitalypb/repository-service.pb.go
index 8c578740f..4b76496ee 100644
--- a/proto/go/gitalypb/repository-service.pb.go
+++ b/proto/go/gitalypb/repository-service.pb.go
@@ -543,10 +543,10 @@ type GarbageCollectRequest struct {
 
 	Repository   *Repository `protobuf:"bytes,1,opt,name=repository,proto3" json:"repository,omitempty"`
 	CreateBitmap bool        `protobuf:"varint,2,opt,name=create_bitmap,json=createBitmap,proto3" json:"create_bitmap,omitempty"`
-	// If set to 'true' the 'gc' will be triggered with '--prune=24.hours.ago' flag.
-	// This will remove dangling objects from the object storage that were not modified in the last 24 hours.
+	// If set to 'true' the 'gc' will be triggered with '--prune=30.minutes.ago' flag.
+	// This will remove dangling objects from the object storage that were not modified in the last 30 minutes.
 	// If 'false' provided the 'gc' will rely on the default expiration period (2 weeks).
-	// The window of 24 hours exists because of possible concurrent operations running on the same
+	// The window of 30 minutes exists because of possible concurrent operations running on the same
 	// storage and removal of the objects may cause races and fail concurrent operations.
 	Prune bool `protobuf:"varint,3,opt,name=prune,proto3" json:"prune,omitempty"`
 }