Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Contribute to a repository you don't own (or simulate it with a partner / a second account): fork it, add an 'upstream' remote, branch, push, and open a pull request. Go through a review cycle (request changes, push fixes), keep your fork in sync with upstream, and resolve at least one real merge conflict correctly. Link the PR to an issue and use a sensible merge strategy.
Fork → branch → push → PR executed correctly; PR is scoped and linked to an issue (Closes #N).
At least one real merge conflict resolved correctly (right final content, markers removed), not blindly accepting one side.
An upstream remote is configured and the fork is kept current (fetch + merge/rebase from upstream).
A genuine review cycle: changes requested and addressed with follow-up commits; sensible merge strategy chosen.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Collaborate through a fork-and-pull-request workflow ## Goal Contribute to a repository you don't own (or simulate it with a partner / a second account): fork it, add an 'upstream' remote, branch, push, and open a pull request. Go through a review cycle (request changes, push fixes), keep your fork in sync with upstream, and resolve at least one real merge conflict correctly. Link the PR to an issue and use a sensible merge strategy. ## Acceptance criteria - [ ] Fork & PR flow: Fork → branch → push → PR executed correctly; PR is scoped and linked to an issue (Closes #N). - [ ] Conflict resolution: At least one real merge conflict resolved correctly (right final content, markers removed), not blindly accepting one side. - [ ] Staying in sync: An upstream remote is configured and the fork is kept current (fetch + merge/rebase from upstream). - [ ] Review etiquette: A genuine review cycle: changes requested and addressed with follow-up commits; sensible merge strategy chosen. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.