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
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ This is accomplished by counting the merges of branches matching the [naming sch
15
15
**Burning Questions**
16
16
17
17
-**Yes** - This can indeed be implemented in repos that previously used different version increment methods.
18
-
-**Yes** - Jira will recognize the issue tag anywhere in the branch name -- it does not have to be a prefix.
18
+
-**Yes** - Jira will recognize the issue tag anywhere in the branch name -- it does not have to be a prefix for the integration to function.
19
19
-**Yes** - This aligns with and extends on [guidance](https://confluence.atlassian.com/bitbucketserver050/using-branches-in-bitbucket-server-913474726.html) from Atlassian on branch naming schemes.
20
20
21
21
> [Convenience link to this action on the marketplace](https://github.com/marketplace/actions/gitops-automatic-versioning)
0 commit comments