Update release documentation.
This commit is contained in:
parent
12c392bde3
commit
c5cdbcfd81
26
README.md
26
README.md
@ -17,18 +17,30 @@ Please see [CONTRIBUTING.md] for the juicy details.
|
||||
|
||||
# Make A New Release
|
||||
|
||||
It's easy. Just tag the current HEAD and run the Make target.
|
||||
Our production site is contained in the [dist folder]. You'll
|
||||
need to make sure you have the latest changes by running:
|
||||
|
||||
```bash
|
||||
$ make proddist
|
||||
```
|
||||
|
||||
If you see any unstaged changes, please verify them with someone and push them
|
||||
to the upstream master remote. Make sure the latest pipeline is passing and tag
|
||||
HEAD with:
|
||||
|
||||
```bash
|
||||
$ git tag -a 2.0.0 $(git rev-parse HEAD)
|
||||
$ git push upstream master
|
||||
$ git push upstream master --tags
|
||||
```
|
||||
|
||||
Then make a release with:
|
||||
|
||||
```bash
|
||||
$ make release
|
||||
```
|
||||
|
||||
This pushes your latest tag to the upstream remote and then
|
||||
takes the contents of the dist folder and pushes it to the
|
||||
production branch.
|
||||
|
||||
Our production setup makes sure to serve this new content.
|
||||
This pushes the contents of the [dist folder] to the production
|
||||
branch which will get picked up by our production instance of
|
||||
the site.
|
||||
|
||||
[dist folder]: https://gitlab.com/autonomic-cooperative/autonomic-cooperative.gitlab.io/tree/master/dist
|
||||
|
Reference in New Issue
Block a user