Skip to content
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

Hooks: Add Source Branch Name to Merge Events #8707

Open
nopcoder opened this issue Feb 24, 2025 · 0 comments · May be fixed by #8703
Open

Hooks: Add Source Branch Name to Merge Events #8707

nopcoder opened this issue Feb 24, 2025 · 0 comments · May be fixed by #8703
Assignees
Labels
area/hooks improvements or additions to the hooks subsystem contributor feature-request

Comments

@nopcoder
Copy link
Contributor

Currently, the merge pre/post events provide information about the destination branch and the source ref as the commit that was used to merge into the branch.

This proposal suggests adding the name of the source branch as part of the merge event data.

Identifying the source branch name during a merge operation offers several benefits:

  • Enforce Branch-Specific Preferences: Different branches might have unique merging requirements or preferences. Knowing the source branch allows for tailored actions based on its origin.
  • Capture Original Request Information: The source branch name provides valuable context about the original merge request, enhancing traceability and understanding of the operation.
@nopcoder nopcoder added area/hooks improvements or additions to the hooks subsystem contributor feature-request labels Feb 24, 2025
@nopcoder nopcoder self-assigned this Feb 24, 2025
@nopcoder nopcoder linked a pull request Feb 24, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/hooks improvements or additions to the hooks subsystem contributor feature-request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant