improvement: automate changelog management (#786)

This commit is contained in:
Thierno IB. BARRY
2020-03-17 14:22:22 +01:00
committed by GitHub
parent ca3d1e1199
commit 9fb1a20d82
11 changed files with 863 additions and 58 deletions

34
.github/CONTRIBUTING.md vendored Normal file
View File

@@ -0,0 +1,34 @@
# Contributing
When contributing to this repository, please first discuss the change you wish to make via issue,
email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
## Pull Request Process
1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
2. Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
3. Once all outstanding comments and checklist items have been addressed, your contribution will be merged! Merged PRs will be included in the next release. The terraform-aws-eks mainteners takes care of updating the CHANGELOG as they merge.
## Checklists for contributions
- [ ] Add [sementics prefix](#semantic-pull-requests) to your PR or Commits (at leats one of your commit groups)
- [ ] CI tests are passing
- [ ] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation
## Semantic Pull Requests
To generate changelog, Pull Requests or Commits must have sementic and must follow conventional specs below:
- `feat:` for new features
- `fix:` for bug fixes
- `improvement:` for enhancements
- `docs:` for documentation and examples
- `refactor:` for code refactoring
- `test:` for tests
- `ci:` for CI purpose
- `chore:` for chores stuff
There is a special prefix `skip changelog` which is skipped during changelog generation. It can be used for `skip changelog: update changelog` commit message by example.

View File

@@ -6,6 +6,5 @@ Please explain the changes you made here and link to any relevant issues.
### Checklist
- [ ] Change added to CHANGELOG.md. All changes must be added and breaking changes and highlighted
- [ ] CI tests are passing
- [ ] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation

14
.github/semantic.yml vendored Normal file
View File

@@ -0,0 +1,14 @@
# By default types specified in commitizen/conventional-commit-types is used.
# See: https://github.com/commitizen/conventional-commit-types/blob/v2.3.0/index.json
# You can override the valid types
types:
- feat
- fix
- improvement
- docs
- refactor
- test
- ci
- chore
- skip changelog
- skip ci

20
.github/workflows/changelog-check.yaml vendored Normal file
View File

@@ -0,0 +1,20 @@
name: CHANGELOG Checks
on:
pull_request:
paths:
- CHANGELOG.md
jobs:
changelog-check:
name: CHANGELOG Check
runs-on: ubuntu-latest
steps:
- name: Fail the check if changelog change
run: |-
echo "Thank you for your contribution!"
echo ""
echo "The 'CHANGELOG.md' file contents are handled by the maintainers during merge. This is to prevent pull request merge conflicts."
echo "Please see the Contributing Guide for additional pull request review items."
echo ""
echo "Remove any changes to the 'CHANGELOG.md' file and commit them in this pull request."
exit 1