[x] The latest changes on the target branch have been incorporated, so that any conflicts are taken care of before merging. This can be accomplished either by merging in the target branch (e.g. 'git merge develop') or by rebasing on top of the target branch (e.g. 'git rebase develop'). Please do not hesitate to reach out to the GenX development team if you need help with this.
[x] I consent to the release of this PR's code under the GNU General Public license.
Before submitting a Pull Request, please ensure you've done the following:
👷♀️ Create small PRs. In most cases, this will be possible. In the case of large feature or module additions, it is best to work towards a "minimum viable product" that is thoroughly tested but may not have all desired functionality or features, make a PR for this, and then later work to add more features.
📝 Use descriptive commit messages.
📗 Update any related documentation.
-->
Post-approval checklist for GenX core developers
After the PR is approved
[ ] Check that the latest changes on the target branch are incorporated, either via merge or rebase
[ ] Remember to squash and merge if incorporating into develop
With Zenodo badge
Description
What type of PR is this? (check all applicable)
Checklist
[x] I consent to the release of this PR's code under the GNU General Public license.
Before submitting a Pull Request, please ensure you've done the following:
-->
Post-approval checklist for GenX core developers
After the PR is approved