Add Working with Gitea

Working-with-Gitea.md

@@ -0,0 +1,24 @@
+## Developer
+1. Check if there are [pull requests needing review](https://gitea.dsv.su.se/DMC/scipro/pulls?type=all&state=open&milestone=0&project=0&assignee=-1)
+2. If yes;
+   1. If there are still in progress actions wait for them to finish
+   2. Assign yourself to the pull request
+   3. Perform the review
+   4. If there are *any* questions; about the code, documentation, test instructions, motivation, or anything else write a comment about it and request changes
+   5. 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
+3. Check which issue is the most prioritized in the [project board](https://gitea.dsv.su.se/DMC/scipro/projects/12) (top of the "Backlog" column)
+4. Assign yourself to the issue
+5. Create a new branch
+6. Start working
+   - Test data
+   - Testing instructions
+   - Automated tests
+   - Documentation
+7. Push your changes
+8. (Optional) Create a draft pull request by prefixing with "WIP: "
+9. 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)
+10. Mark it with the label "po/needed" if you want the product owner to check the changes
+11. Keep the pull request up to date. Most of the time clicking the automated "Update branch by merge" button in Gitea is enough.