- We work in 2-week sprints
- @seberatolmez and @dogukanurker assign tasks
- Each task has priority and effort labels
- Check the GitHub Project board for your assigned tasks
- Go to Issues tab in GitHub
- Click New issue
- Fill in:
- Title: Short description (e.g., "Add login page")
- Description: Details, acceptance criteria
- Labels:
bug,feature,docs, etc. - Assignees: Who will work on it
- Sprint: Select current sprint from Projects
- Click Submit new issue
After pushing your branch:
- Go to Pull requests tab
- Click New pull request
- Select your branch to merge into
main - Fill in:
- Title: What this PR does
- Description:
- What changed
- Link to issue:
Closes #123
- Reviewers: Add at least 1 reviewer (admin)
- Assignees: Yourself
- Click Create pull request
- On the PR page, find Reviewers on the right sidebar
- Click the gear icon
- Add reviewers (at least one admin):
seberatolmezORdogukanurker
- They will be notified
At least one admin approval is required before your PR can be merged.
- Go to Files changed tab
- Review the code
- Add comments if needed (click the
+on any line) - Submit review:
- Approve: Code is good
- Request changes: Needs fixes
- Comment: Just feedback
- Address review comments
- Push fixes to the same branch
- Request re-review if needed
- PRs must be reviewed by at least one admin:
@seberatolmezOR@dogukanurker
- At least one approval required before merging
- All checks (linting) must pass
- Only admins can merge to
main - Always use "Squash and merge" (not regular merge)
- Click the dropdown arrow on the green merge button
- Select "Squash and merge"
- Edit the commit message if needed
- Click confirm
This combines all your commits into one clean commit.
In PR description, use:
Closes #123- closes issue when PR mergesFixes #123- same as closesRelates to #123- links without closing