-
Notifications
You must be signed in to change notification settings - Fork 2
Contributing
Mariana Almeida edited this page Mar 13, 2026
·
5 revisions
The full contributing guide lives alongside the code so it's always in sync with the develop branch:
Find/open issue → get assigned by PM → branch from milestone branch
→ implement → PR into milestone branch → review → merge
↓
milestone branch → develop (when milestone is stable)
Issues are assigned by the project manager — do not self-assign. Ask to be assigned.
| Milestone | Branch to target |
|---|---|
| Feup Exchange | feature/exchange |
| Collaborative Sessions | feature/collaborative-sessions |
| Random Features | develop |
feat/<description> fix/<description> refactor/<description>
style/<description> chore/<description> docs/<description>
Branch from the milestone branch, not from develop:
git checkout feature/exchange
git checkout -b feat/my-feature-
Closes #<issue>in the description - The correct milestone branch as the target
- A milestone assigned in the sidebar
- A reviewer assigned
feat(scope): add exchange request modal
fix(admin): redirect unauthenticated users to login
See the full guide for code standards, PR size guidelines, and wiki update expectations.