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
Been struggling for a while to get the Pull Request merge versions right. Either Azure Repos/VSTS changed something or we did it manually for a while, overriding the default.
I just tested and the default message is: Merge pull request 443 from hotfix/2.17.7 into master.
It'd be great if someone could confirm the above is indeed the default message for them as well (couldn't find any docs).
If this'd be appreciated I'd be very happy to shoot in a pull request for it.
The text was updated successfully, but these errors were encountered:
This is what our Azure devops merge message looks like: Merged PR 1234: A custom PR title
What I do when creating a release is actually changing the title to the merge message GitVersion expect, as in: Merge branch 'release/1.0'. This way the git message is detected by GitVersion.
It would be great if GitVersion would just look for the branch name release/1.0 when the pull request is merged with master branch.
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.
Been struggling for a while to get the Pull Request merge versions right. Either Azure Repos/VSTS changed something or we did it manually for a while, overriding the default.
I just tested and the default message is:
Merge pull request 443 from hotfix/2.17.7 into master
.It'd be great if someone could confirm the above is indeed the default message for them as well (couldn't find any docs).
If this'd be appreciated I'd be very happy to shoot in a pull request for it.
The text was updated successfully, but these errors were encountered: