NOTE: We use conventional commits, which means semantic commit messages. Please adhere to these prefixes. Pull requests must also have a semantic prefix, e.g. 'feat:' or 'fix:'. If you are doing multiple changes at once, you are probably doing too much at once. Opt for smaller but more pull requests.
- Fork this repo.
- Change the code and push to <your_branch>.
- Edit the main yaml of your QMS flow and edit the GitHub service connection to look like this:
- repository: qms_pipeline_templates
type: github
name: <your_GH_user>/qms-pipeline-templates
endpoint: GH_public_service_connection
ref: <your_branch>
- Rerun your flow and test the code changes fix your issue or implement your feature.
- Possibly take a couple of screenshots for documenting the change.
- Create a PR, append evidence and notify the QMS TEAM.
- QMS team reviews the PR.
- Merge the PR to main.
- Run the ADO pipeline nightly flow or wait for the nightly build to check that the changes didn't break the overall flow.
NOTE You can perform the subsequent two steps with this script
- Tag the latest commit with the last available tag
git tag <your_version>
- Push the tag to origin
git push origin <your_version>
- Point to new qms-pipelines templates in cli and bump the version as in this guide.
- Thank the contributor(s) and inform them that their changes are availble at the latest tag.