Skip to content

Instantly share code, notes, and snippets.

@gambitier
Created October 24, 2023 16:41
Show Gist options
  • Select an option

  • Save gambitier/7416b487778a46842d3752c019a27083 to your computer and use it in GitHub Desktop.

Select an option

Save gambitier/7416b487778a46842d3752c019a27083 to your computer and use it in GitHub Desktop.
Creating Github Release Notes

Creating Github Release Notes

Configuring automatically generated release notes

image

To generate release note as seen in screenshot

  1. PR should follow some naming convention for title and #ISSUE-NUMBER must be present in pr title (based on this titles are created in release note)
  2. PR should attach proper labels (based on this categorisation works)

PR Naming convention

<type> #<github-issue-number>: <short-description>

Type

  • build - Changes that affect the build system or external dependencies (dependencies update)

  • ci - Changes to our CI configuration files and scripts (basically directory .github/workflows)

  • docs - Documentation only changes

  • feat - A new feature

  • fix - A bug fix

  • chore - Changes which does not touch the code (ex. manual update of release notes). It will not generate release notes changes

  • refactor - A code change that contains refactor

  • style - Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)

  • test - Adding missing tests or correcting existing tests and also changes for our test app

  • perf - A code change that improves performance (I do not think we will use it)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment