feat: implementing ansys/actions/changelogs and adding release note in documentation

[clatapie]

Implementing release note in documentation, using ansys/actions/changelogs and ansys/pyansys-geometry#1138.

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.17%. Comparing base (de18185) to head (0e51264).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3019      +/-   ##
==========================================
- Coverage   86.63%   84.17%   -2.47%     
==========================================
  Files          52       52              
  Lines        9550     9550              
==========================================
- Hits         8274     8039     -235     
- Misses       1276     1511     +235     

[germa89]

Is this still a draft? @clatapie

[clatapie]

The changelog can be effective but I wanted to add some documentation about commit and branch name conventions. I also have planned to add the ansys/action that checks those names as pyansys-geometry does.

[clatapie]

I will resume it next week

[clatapie]

As the Contributing section in the PyAnsys dev guide details the naming conventions, adding the action should be enough to ensure a consistent changelog section.
Pinging @germa89 for visibility.

[germa89]

For reference: https://dev.docs.pyansys.com/how-to/contributing.html#commit-naming-conventions

Contributing — PyAnsys developer's guide

[germa89]

I think you should add the documentation the new branch and commit names. Also mentioned the update changelog feature. Especially, if the developer needs to take something into account. Like write a meaningful PR name or similar.

Otherwise LGTM. Thank you for this @clatapie