Add make release (#176)

Signed-off-by: Steffen Exler <steffen.exler@pm.me> Signed-off-by: Steffen Exler <steffen.exler@pm.me>
SchwarzIT · Nov 4, 2022 · 5eb33e5 · 5eb33e5
1 parent 9e00552
commit 5eb33e5
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 2 deletions.
diff --git a/Makefile b/Makefile
@@ -93,6 +93,9 @@ testing-project-ci:  ## Creates for all yml files in ./test_project_values a tes
 		make testing-project-ci-single VALUES_FILE=$$VALUES; \
 	done
 
+.PHONY: release
+release:  ## Create a new release version
+	@./hack/release.sh
 
 help:
 	@echo 'Usage: make <OPTIONS> ... <TARGETS>'

diff --git a/README.md b/README.md
@@ -35,9 +35,10 @@ If you have Go 1.16+, you can directly install by running:
 go install github.com/schwarzit/go-template/cmd/gt@latest
 ```
 
-> Based on your go configuration the `go/template` binary can be found in `$GOPATH/bin` or `$HOME/go/bin` in case `$GOPATH` is not set. 
+> Based on your go configuration the `go/template` binary can be found in `$GOPATH/bin` or `$HOME/go/bin` in case `$GOPATH` is not set.
 > Make sure to add the respective directory to your `$PATH`.
 > [For more information see go docs for further information](https://golang.org/ref/mod#go-install). Run `go env` to view your current configuration.
+
 #### From the released binaries
 
 Download the desired version for your operating system and processor architecture from the [go-template releases page](https://github.com/SchwarzIT/go-template/releases).

diff --git a/docs/release.md b/docs/release.md
@@ -10,7 +10,7 @@ To create a new release please do the following:
 
 - Checkout the main branch
 - `git pull` to update it
-- Execute `hack/release.sh` to create a new release PR (if you don't have the GitHub CLI installed you need to create the PR yourself from the branch that was created by the script)
+- Execute `make release` to create a new release PR (if you don't have the GitHub CLI installed you need to create the PR yourself from the branch that was created by the script)
 - Get someone else to approve your PR. This also ensures that all maintainers agree that a new version should be released
 - After the PR is merged, the workflow `tag-release` should be executed automatically
   - This workflow listens to all changes on the `config/version.txt` file