feat(runway): Add CommitMessageResolver interface for squash and merge commit metadata - #767
Merged
Merged
Conversation
…e commit metadata
manjari25
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
October 2, 2026 03:11
behinddwalls
approved these changes
Oct 2, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
Squash and merge commits need a message and author, and the source differs by deployment. OSS can use a synthetic message, while other deployments may pull richer metadata from their code review platform. Making it an injected dependency lets the unified merger stay provider- and deployment-agnostic. The merger will start using it in the next PR.
What?
Adds
merger.CommitMessageResolverandmerger.CommitMessagetorunway/extension/merger/, plus a generated mock. The resolver returns the message and authorship for the change a URI names.Test Plan
make check-gazelle,make check-tidyandmake lintpass.bazel build //runway/...passes.Issue