First one is creating/updating draft release to simplify release process. Action is done right after Pull Request to master is merged. It is using the Pull Release titles to construct changelog. You can modify how the changelog will look like by adding labels to Pull Requests.
Sections:
Added Features - label feature
Changed Features - label enhancement
Bug Fixes - label bug
Maintenance - label documentation or chore
Second workflow is simply checking Python code for each commit. It is verifying the code consistency, common code style rules defined by Python organisation (PEP8). It will benefit to verify if the committed code is valid.
Created two GitHub workflows.
First one is creating/updating draft release to simplify release process. Action is done right after Pull Request to master is merged. It is using the Pull Release titles to construct changelog. You can modify how the changelog will look like by adding labels to Pull Requests.
Sections: Added Features - label feature Changed Features - label enhancement Bug Fixes - label bug Maintenance - label documentation or chore
Second workflow is simply checking Python code for each commit. It is verifying the code consistency, common code style rules defined by Python organisation (PEP8). It will benefit to verify if the committed code is valid.
To enable GitHub Actions for your repository: https://github.com/features/actions
How the output look like of the Actions feature you can look at: https://github.com/mklemarczyk/MB-Lab/actions