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
+5-29Lines changed: 5 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,38 +40,14 @@ Projects using this must ensure the necessary POM sections are overriden - these
40
40
41
41
Once you have configured your project and environment you can release to Maven Central. It may look a little something like the examples below.
42
42
43
-
### Example Releasing
44
-
The golden rule is ALWAYS do this on a separate branch (it makes [backing out](https://github.com/BorderTech/java-common/wiki/Releasing#dealing-with-failure) much easier when problems arise).
43
+
### Releasing
44
+
The golden rule is ALWAYS do the release on a separate branch (it makes [backing out](https://github.com/BorderTech/java-common/wiki/Releasing#dealing-with-failure) much easier when problems arise).
45
45
46
-
```bash
47
-
# make sure you are on the main/default branch
48
-
git checkout master # or "git checkout bobbie" etc
46
+
Full documentation is available in the wiki under [Releasing](https://github.com/BorderTech/java-common/wiki/Releasing).
49
47
50
-
# fetch latest changes from main repository
51
-
git fetch origin # or "git fetch upstream" if you are on a fork
48
+
It is recommended projects use [gitflow with pull requests](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) model (ie feature, develop, release, master, hotfix branch paradigm).
52
49
53
-
# ensure local branch is up-to-date
54
-
git merge origin/master # or "git merge upstream/master" or "git merge upstream/bobbie" etc
55
-
56
-
# create a new release branch (you could skip this step if it already exists which it probably shouldn't)
0 commit comments