Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Lagoon project for "release-drafter" Github Action #1534

merged 1 commit into from Jan 13, 2020


Copy link

tobybellwood commented Jan 7, 2020

This PR enables the use of the release-drafter GitHub action to auto-create release notes ahead of the next release of Lagoon.

This uses two pieces of information:

  • The PR title - very important to keep this concise and to-the-point (it's now a proxy changelog entry)
  • The subsystem label(s) assigned for use - named [0-9]-subsystem.

It'll auto-generate a draft of the next minor release of Lagoon for us, and keep track of all the PRs merged into master and develop branches between releases. This also allows us to go back and reword a PR title, or re-assign a label as necessary, and the release notes will be modified on the next run. I've reworded the PR template accordingly.

We should trial this for a release or two - I've proposed a PR title-based system to allow more freedom in commit message titling. There is the ability to use a skip-changelog label to not include a PR in the list, but these will be reviewed prior to the next release being produced.

@tobybellwood tobybellwood added this to the v1.3.0 milestone Jan 7, 2020
@tobybellwood tobybellwood added this to Lagoon 1.3.0 (Jan 2020) in Lagoon Roadmap (Indicative) Jan 7, 2020
@Schnitzel Schnitzel merged commit 1070917 into amazeeio:master Jan 13, 2020
1 check passed
1 check passed
continuous-integration/jenkins/pr-merge This commit looks good
@tobybellwood tobybellwood removed this from Lagoon 1.3.0 (Jan 2020) in Lagoon Roadmap (Indicative) Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.