build(retrocookie): reflect updates to source template from generated…

… project 'science-institute_brain-lab'

datajoint-workflow/{{cookiecutter.github_repo}}/CONTRIBUTING.md

@@ -72,9 +72,8 @@ Format your commit messages so that they help create the appropriate semantic ve
 
 _Conventional Commit Resources_:
 
-- [Conventional commits](https://www.conventionalcommits.org/en/v1.0.0-beta.4/)
-- [More commit examples](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional)
-- [Angular format](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commit-message-format)
+- [`semantic-release`: GitHub Action used with this package](https://github.com/semantic-release/semantic-release)
+- Other [conventional](https://www.conventionalcommits.org/en/v1.0.0-beta.4/) commit [examples](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) and [resources](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commit-message-format)
 
 !!! tip "Commit History"
     Writing a [descriptive commit message](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commit-message-format) is highly recommended. In case of doubt, you can check the commit history to look for recurring communication patterns with: