Skip to content

feat(runway): Add CommitMessageResolver interface for squash and merge commit metadata - #767

Merged
behinddwalls merged 1 commit into
mainfrom
manjari/commit-message-resolver
Oct 2, 2026
Merged

behinddwalls merged 1 commit into
mainfrom
manjari/commit-message-resolver

Conversation

@manjari25

Copy link
Copy Markdown
Contributor

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.CommitMessageResolver and merger.CommitMessage to runway/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-tidy and make lint pass.
  • bazel build //runway/... passes.
  • No behavior change, since nothing consumes the interface yet

Issue

@manjari25
manjari25 requested review from a team, behinddwalls and sbalabanov as code owners October 2, 2026 03:11
@behinddwalls
behinddwalls added this pull request to the merge queue Oct 2, 2026
Merged via the queue into main with commit 3e00396 Oct 2, 2026
16 checks passed
@behinddwalls
behinddwalls deployed to stack-rebase October 2, 2026 13:43 — with GitHub Actions Active
@behinddwalls
behinddwalls deleted the manjari/commit-message-resolver branch October 2, 2026 13:43

This branch was successfully deployed

1 active deployment
stack-rebase — 7e37a5c2 Deployed Oct 2, 2026 by behinddwalls via Rebase Stack #553
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants