If there are still in progress actions wait for them to finish
Assign yourself to the pull request
Perform the review
If there are any questions; about the code, documentation, test instructions, motivation, or anything else write a comment about it and request changes
Once approved - if it is labelled with "po/approved" or has no "po" label then squash merge it into develop
Clean up the commit message if necessary
Check which issue is the most prioritized in the project board (top of the "Backlog" column)
Assign yourself to the issue
Create a new branch
Start working
Test data
Testing instructions
Automated tests
Documentation
Push your changes
(Optional) Create a draft pull request by prefixing with "WIP: "
Submit a pull request (targetting the develop branch)
Document how to test
Reference any issues that the changes address using "Fixes #N" (check that the "Fixes" text has dotted underline to ensure it's linked correctly)
Mark it with the label "po/needed" if you want the product owner to check the changes
Keep the pull request up to date. Most of the time clicking the automated "Update branch by merge" button in Gitea is enough.