We use a Draft Pull Request workflow to manage contributions effectively.
This tab is the central space for communication to see what peers are working on.
- Pick and issue from the Issues tab, consider using a suitable filter like good first issue. (See also CONTRIBUTING_issues_tab.md)
- Check the Pull Requests Tab.
- Submit an initial commit and convert to a
pull request. - convert your pull request to
draft(illustration below) - reference the existing issue with the # feature e.g.
#134. - convert the PR to an open pull request when ready!
- pull from
mainbranch to ensure no merge conflicts betweenbranchandmain - run
cd frontend; npm run buildcausing no typescript errors - include # in description e.g. #243. This links the pull request to issue(s) solved
- add screenshots and or screen recordings of the new outcome
Optional: to request the code owner team to manually test the branch in their IDE, you can add the label action required: manual testing
template provided here.
- Everyone is a contributor.
- The Code owners have the additional role to review + merge the pull requests.
- Our current code owners are Laurie, Joseph, Aznim and Viola -- feel free to reach out to us on the Discord channel :)
- As per the branch rules, 1 code owner approval is sufficent to merge a Pull Request.
- Review description of PR, check for steps 1-4 mentioned above.
- Assign a relevant label if necessary for
action required. - Review the
files changedtab. - Approve when ready.
- Merge.
example labels:
Q: How do I get assigned to an issue? A: The best way to self-assign is by drafting a Pull Request. Just check the Pull Requests Tab for potential overlap.
Q: I want to work on an issue. Is it acceptable to pull request an initial commit with no changes?
A: Yes! Just make sure it is marked as draft.
Q: I want to work on an issue but someone has started working on it in the Pull Request drafts. A: If someone has started on the Pull Requests Tab, consider reaching out to that peer in the comments and offering to contribute an isolated issue to their branch.
Please read CONTRIBUTING_issues_tab.md for further guidance on using the issues tab.
if you haven't already:



