You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Strategy defines the possible source control integration methods
33
+
enumStrategy {
34
+
// Default strategy (let server decide based on configuration)
35
+
STRATEGY_DEFAULT=0;
36
+
// Rebase commits onto target branch before landing
37
+
STRATEGY_REBASE=1;
38
+
// Same as REBASE but squash commits into a single commit before rebase
39
+
STRATEGY_SQUASH_REBASE=2;
40
+
// Merge commits into the target branch by creating a separate merge commit, preserving the commit history along with hashes
41
+
STRATEGY_MERGE=3;
42
+
}
43
+
44
+
// Change represents a set of related code changes identified by one or more IDs from a particular code change provider, like Github Pull Requests.
45
+
messageChange {
46
+
// The code change provider (e.g., "github", "gerrit", "phabricator").
47
+
stringsource=1;
48
+
// List of change IDs, in a format specific to the code change provider, that should be landed together. SubmitQueue guarantees that the changes are landed in the order of the list,
49
+
// and no other changes are landed in between. SubmitQueue does not guarantee that each change is individually valid, but produces a special validity
50
+
// marker on such changes. The user is responsible to include all changes in a change stack in the order of the list, starting from the earlist change.
51
+
repeatedstringids=2;
52
+
}
53
+
54
+
// LandRequest defines a request to land (merge into target branch of the source control repository) a set of code changes.
55
+
messageLandRequest {
56
+
// Name of the queue processing the land request. The queue should be defined in the configuration, otherwise an error is returned.
57
+
stringqueue=1;
58
+
// Change (such as a pull request) to land into the target branch. Target branch is defined by the queue configuration.
59
+
Changechange=2;
60
+
// Source control integration strategy to use for this land operation. If not specified, the default queue strategy is used.
61
+
Strategystrategy=4;
62
+
}
63
+
64
+
// LandResponse defines the response to a land request.
65
+
messageLandResponse {
66
+
// Globally unique identifier for the land request. Used to track the land request lifecycle.
67
+
stringsqid=1;
68
+
}
69
+
70
+
// ***************
71
+
// Error messages, returned as `google.rpc.Status` messages.
72
+
// ***************
73
+
74
+
// Generic error with metadata. Each custom error type should extend this message.
75
+
messageError {
76
+
// Free text error message describing the error.
77
+
stringmessage=1;
78
+
}
79
+
80
+
// UnrecognizedQueueError is returned when a queue name is not recognized. Typically this indicates a typo in the queue name or server misconfiguration.
81
+
messageUnrecognizedQueueError {
82
+
// Free text error message describing the error.
83
+
Errorerror=1;
84
+
// Name of the queue that was not recognized.
85
+
stringqueue=2;
86
+
}
87
+
88
+
// ***************
89
+
// Service definitions.
90
+
// ***************
91
+
28
92
// SubmitQueueGateway provides the gateway API
29
93
serviceSubmitQueueGateway {
30
94
// Ping returns a response indicating the service is alive
31
95
rpcPing(PingRequest) returns (PingResponse) {}
96
+
97
+
// Land lands a set of code changes into a target branch, performing the necessary validations across all other changes in the queue.
98
+
// The processing is asynchronous and returns a LandResponse immediately. The land request is processed in the background.
0 commit comments