README
¶
Runway
Runway owns the merge queues defined by the external contract in
api/runway/messagequeue: it consumes merge-conflict-check and merge
requests, performs the work, and (eventually) publishes the result to the corresponding signal queue.
SubmitQueue is a client of these queues.
Runway is a single service (the domain is the service); its controllers live directly under
controller/. It consumes Runway's merge queues:
merge-conflict-check— dry-run check that an ordered sequence of merge steps applies cleanly, without committing.merge— committing merge: apply and commit the ordered steps.
Both controllers currently deserialize the MergeRequest off the queue and log it; performing the
merge and publishing a MergeResult to the corresponding signal queue is not wired yet.
Directories
¶
| Path | Synopsis |
|---|---|
|
merge
Package merge consumes committing merge requests from Runway's merge queue.
|
Package merge consumes committing merge requests from Runway's merge queue. |
|
mergeconflictcheck
Package mergeconflictcheck consumes dry-run merge-conflict check requests from Runway's merge-conflict-check queue.
|
Package mergeconflictcheck consumes dry-run merge-conflict check requests from Runway's merge-conflict-check queue. |
|
Package extension holds Runway-specific extension implementations.
|
Package extension holds Runway-specific extension implementations. |
|
merger
Package merger defines the pluggable interface for version-control merge operations that Runway performs on behalf of its callers.
|
Package merger defines the pluggable interface for version-control merge operations that Runway performs on behalf of its callers. |
|
merger/mock
Package mock is a generated GoMock package.
|
Package mock is a generated GoMock package. |
|
merger/noop
Package noop provides a no-op Merger implementation for local development and testing.
|
Package noop provides a no-op Merger implementation for local development and testing. |
Click to show internal directories.
Click to hide internal directories.