Skip to content

Commit

Permalink
chore(ci): configure release-please, update contrib (#122)
Browse files Browse the repository at this point in the history
  • Loading branch information
noahdietz committed Aug 18, 2023
1 parent 97c970d commit e69e468
Show file tree
Hide file tree
Showing 3 changed files with 38 additions and 0 deletions.
20 changes: 20 additions & 0 deletions .github/workflows/release.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: release-please
on:
push:
branches:
- master

permissions:
contents: write
pull-requests: write

jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: google-github-actions/release-please-action@v3
with:
release-type: go
package-name: uuid
skip-labeling: true
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
# Changelog

16 changes: 16 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,22 @@

We definitely welcome patches and contribution to this project!

### Tips

Commits must be formatted according to the [Conventional Commits Specification](https://www.conventionalcommits.org).

Always try to include a test case! If it is not possible or not necessary,
please explain why in the pull request description.

### Releasing

Commits that would precipitate a SemVer change, as desrcibed in the Conventional
Commits Specification, will trigger [`release-please`](https://github.com/google-github-actions/release-please-action)
to create a release candidate pull request. Once submitted, `release-please`
will create a release.

For tips on how to work with `release-please`, see its documentation.

### Legal requirements

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

0 comments on commit e69e468

Please sign in to comment.