Skip to content

Enforce the use of Change-Id in each commit #183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2025
Merged

Conversation

jserv
Copy link
Contributor

@jserv jserv commented Feb 19, 2025

To prepare for code review systems like Gerrit, every git commit message must include a Change‑Id.

Gerrit groups commits into a single review using a Change-Id in the commit message footer. e.g., if a change needs updating, a follow-up commit can address issues, and Gerrit will link the new version to the original review—even across cherry-picks and rebases.

Reference:
https://gerrit-review.googlesource.com/Documentation/user-changeid.html

Change-Id: Ib344622a3887387f9ac954dcd599c4ba45836419

To prepare for code review systems like Gerrit, every git commit message
must include a Change‑Id.

Gerrit groups commits into a single review using a Change-Id in the
commit message footer. e.g., if a change needs updating, a follow-up
commit can address issues, and Gerrit will link the new version to the
original review—even across cherry-picks and rebases.

Reference:
  https://gerrit-review.googlesource.com/Documentation/user-changeid.html

Change-Id: Ib344622a3887387f9ac954dcd599c4ba45836419
@jserv jserv merged commit 0b8be2c into master Feb 19, 2025
4 checks passed
@jserv jserv deleted the enforce-changeid branch February 19, 2025 21:19
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.

1 participant