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
Language/content agnostic method of automatically determining the [semantic version](https://semver.org/) for a product based on _branch_ merge history with MINIMAL discipline dependencies.
11
+
Language/content agnostic method of automatically determining the [semantic version](https://semver.org/) for a product based on _branch_ merge history with MINIMAL [discipline dependencies](https://github.com/marketplace/actions/gitops-automatic-versioning?#discipline-dependency).
12
12
13
13
This is accomplished by counting the merges of branches matching the [naming scheme](#branch-naming-scheme) into the [main|master] branch. Folks familiar with Scrum/SAFe or GitFlow/fooFlow strategies will recognize this scheme.
14
14
15
-
**Yes**, this can be implemented in repos that previously used different version increment methods.
15
+
**Burning Questions**
16
+
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 for the integration to function.
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.
16
20
17
21
> [Convenience link to this action on the marketplace](https://github.com/marketplace/actions/gitops-automatic-versioning)
18
22
23
+
## Recent Changes
24
+
25
+
- 1.0.0: (non-breaking) Addition of support for mono-repos. IE: Discretely version specific directories.
26
+
- NOTE: Github, Jira, etc., were designed to host one product per repo/project. DO NOT create new mono-repo projects unless you're specifically tooling out to support them well.
27
+
- 0.3.1: Update the checkout action version to v4.
28
+
- 0.3.0: Bring back the unshallowing, which ensures the full git log is available.
29
+
- TODO: Adjust scripts to use `git log --remotes` to avoid unshallowing large repos.
30
+
- 0.2.9: Fix 'ops' increments; add user friendly error outputs.
@@ -254,5 +303,5 @@ For those interested, here's some pseudo code:
254
303
PRs are welcome.
255
304
256
305
- input(s): iteration-branches (map) - inform MINOR and PATCH incrementing branch name patterns.
257
-
- input(s): mono-mode (bool) - version subdirs discretely
258
-
-~~CAN'T DO~~: DONE: unshallow from last version tag to latest commit to... Seems a limitation of (git at first glance). See the [Checkout From Tag](https://github.com/marketplace/actions/checkout-from-tag) action.
306
+
-DONE: input(s): mono-mode (bool) - version subdirs discretely
307
+
-UNDONE-CAN'T DO: ~~CAN'T DO~~: ~~DONE:~~ unshallow from last version tag to latest commit to... Seems a limitation of (git at first glance). See the [Checkout From Tag](https://github.com/marketplace/actions/checkout-from-tag) action.
echo -e "[$(${tsCmd})] \e[01;31mERROR\e[00m: 520 - You must source this script when specifying an environment variable! Eg: '. ./${0##*/} -e foo_ver'\n"
170
-
echo"::error title=Usage Error::ERROR 520 - You must source this script when specifying an environment variable! Eg: '. ./foo.sh -e bar_ver'"
0 commit comments