Fix force push to develop on master hotfixes

[bdmendes]

Review checklist

• Terms and conditions reflect the current change
• Contains enough appropriate tests
• If aimed at production, writes a new summary in whatsnew/whatsnew-pt-PT
• Properly adds an entry in changelog.md with the change
• If PR includes UI updates/additions, its description has screenshots
• Behavior is as expected
• Clean, well-structured code

[LuisDuarte1]

LGTM, just check if the push force permission is only on the @niaefeup-admin account on the develop branch

We should discuss some changes that must be done by fixes to master

[LuisDuarte1]

I dismissed the review, because I have some further thoughts into this to make fixes into master simpler. Also maybe we should look into not bumping the minor version on master if the push doesn't come from develop, and instead bump the patch version.

[LuisDuarte1]

Maybe if the master does not match the develop branch, we should create automatically create a PR to accommodate such fixes to the develop branch

[LuisDuarte1]

In this way we can adopt the fix workflow that we discussed in the past Thursday meeting:

1. Make fix on the master branch
2. Make a PR into the master branch
3. Upon merging, the action will automatically create a PR to merge this changes into develop
4. If necessary, do some fixes to work in the develop branch
5. Upon approval, merge into develop

I think this is the most streamlined and error-free approach into getting fixes done in master but also in develop.
Maybe this should be a seperate action workflow, and maybe done on a seperate issue, that listens to merged pull request events into `master, wdyt?

[bdmendes]

Sure, we can create a separate workflow listening for merged pull requests to master or simply pushes, that compares to develop and finds if it needs backporting. I think that should go on another issue since it is not related to this hotfix.

[LuisDuarte1]

With that said, maybe you should change the base of this PR to master and not to develop 😅
Just to be consistent with this workflow, from now on.

[codecov]

Codecov Report

Merging #930 (e21a273) into master (c49573c) will not change coverage.
Report is 2 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@          Coverage Diff          @@
##           master   #930   +/-   ##
=====================================
  Coverage      23%    23%           
=====================================
  Files         143    143           
  Lines        4351   4351           
=====================================
  Hits          959    959           
  Misses       3392   3392