You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 26, 2022. It is now read-only.
When I have the merge config set to merge the PR on all approvals, the merge that results overwrites the PR's change title such that if I have tags in my PR title that are needed by my CI/CD process, then those tags are lost.
We use tagging in the PR title to signify additional things the build should do for that PR -> like increment version numbers, tagging, issue resolution, etc.
Checks-out breaks this functionality when merge is set to enabled.
so either checks-out should append to that or provide an option to not do that.
Example:
My PR Title: [MAJOR] This adds breaking functionality
Checks-out merges with change title:
Merged by checks-out
Approved by:
<person>
I would expect it to be:
[MAJOR] This adds breaking functionality
Merged by checks-out
Approved by:
<person>
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I have the merge config set to merge the PR on all approvals, the merge that results overwrites the PR's change title such that if I have tags in my PR title that are needed by my CI/CD process, then those tags are lost.
We use tagging in the PR title to signify additional things the build should do for that PR -> like increment version numbers, tagging, issue resolution, etc.
Checks-out breaks this functionality when merge is set to enabled.
so either checks-out should append to that or provide an option to not do that.
Example:
My PR Title:
[MAJOR] This adds breaking functionality
Checks-out merges with change title:
I would expect it to be:
The text was updated successfully, but these errors were encountered: