Skip to content

Commit e69e468

Browse files
authored
chore(ci): configure release-please, update contrib (#122)
1 parent 97c970d commit e69e468

File tree

3 files changed

+38
-0
lines changed

3 files changed

+38
-0
lines changed

.github/workflows/release.yaml

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: release-please
3+
on:
4+
push:
5+
branches:
6+
- master
7+
8+
permissions:
9+
contents: write
10+
pull-requests: write
11+
12+
jobs:
13+
release-please:
14+
runs-on: ubuntu-latest
15+
steps:
16+
- uses: google-github-actions/release-please-action@v3
17+
with:
18+
release-type: go
19+
package-name: uuid
20+
skip-labeling: true

CHANGELOG.md

+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Changelog
2+

CONTRIBUTING.md

+16
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,22 @@
22

33
We definitely welcome patches and contribution to this project!
44

5+
### Tips
6+
7+
Commits must be formatted according to the [Conventional Commits Specification](https://www.conventionalcommits.org).
8+
9+
Always try to include a test case! If it is not possible or not necessary,
10+
please explain why in the pull request description.
11+
12+
### Releasing
13+
14+
Commits that would precipitate a SemVer change, as desrcibed in the Conventional
15+
Commits Specification, will trigger [`release-please`](https://github.com/google-github-actions/release-please-action)
16+
to create a release candidate pull request. Once submitted, `release-please`
17+
will create a release.
18+
19+
For tips on how to work with `release-please`, see its documentation.
20+
521
### Legal requirements
622

723
In order to protect both you and ourselves, you will need to sign the

0 commit comments

Comments
 (0)