investigate release notes automation

[joshuadkitenge]

Description

Added configuration for custom auto generated release notes.
Made relevant changes in documentation.

The same changes would need to be made in ims-api

Testing instructions

Add a set up instructions describing how the reviewer should test the code

• Review code
• Check Actions build
• Review changes to test coverage
• {more steps here}

Agile board tracking

closes #806

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.13%. Comparing base (d8e1be1) to head (1ab603f).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #962   +/-   ##
========================================
  Coverage    99.13%   99.13%           
========================================
  Files           89       89           
  Lines        17572    17572           
  Branches      2130     2129    -1     
========================================
  Hits         17420    17420           
  Misses         151      151           
  Partials         1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[joelvdavies]

Only looked at the branch names, had some thoughts, happy to discuss further.

[joelvdavies]

Do these work with multiple? Could docs/documentation work for example? I personally prefer docs but then some others can't be shortened.

Same for feat/feature.

Thinking about it, perhaps its worth aligning closer with https://www.conventionalcommits.org/en/v1.0.0/ (This is what DAFNI used, although they are for commits instead)?

[joshuadkitenge]

https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#type

[joelvdavies]

Suggested change

	- head-branch: ['^bug/']
	- head-branch: ['^fix/']

I think the branch names tend to be more to do with that they do, so this is normally fix.

[joelvdavies]

Perhaps this and dependency if possible.

[joelvdavies]

Following on from these being what they do, perhaps enhance/? Or even improve/.

[joelvdavies]

Suggested change

	- head-branch: ['^removed/']
	- head-branch: ['^remove/']