Each week you will have an issue assigned to you.
To work on your issue, you should create a new branch in your repository.
Use the following naming convention:
assignment(no.)/issue(no.)
Example:
assignment1/issue3
Create and switch to your new branch:
git checkout -b assignment1/issue3main branch. Keeping main clean ensures you can always pull updates from the class repository without issues.
Work on your assignment and complete the requirements of the issue.
All pull requests must include tests for any new or modified behaviour. PRs without adequate test coverage will not be merged.
See TESTING.md for full documentation on the test suite, including how to run tests, how to write API route, component, and end-to-end tests, and how to mock Supabase and fetch.
- New API routes must have unit tests covering at minimum: a valid request, an invalid/missing field, and any error cases (conflicts, database errors).
- New or modified components must have unit tests covering any user interactions or validation logic.
- Significant new user-facing flows must have a Playwright end-to-end test covering the happy path.
- All tests must pass before opening a PR. Run the full check suite locally first:
npm run checkThis runs type checking, linting, unit tests, and end-to-end tests in sequence. If any step fails, fix it before submitting.
When you're ready to save your work:
git add .
git commit -m "Add a descriptive commit message here"Your commit message should clearly describe what you changed.
Push your branch to your fork (origin):
git push origin assignment1/issue3-
Go to your repository on GitHub
-
You should see a prompt to create a pull request for your recently pushed branch
- If not, click the Pull Requests tab and then click New Pull Request
-
Make sure the following are correct:
- Base repository: danwhite-osucascades/cs464
- Base branch: main
- Head repository: YOUR_USERNAME/cs464
- Compare branch: assignment1/issue3
-
Add a clear title and description explaining what you implemented
-
Click Create pull request
- Your pull request will be reviewed
- You may receive feedback or requested changes
- If changes are requested, make updates on the same branch and push again:
git add . git commit -m "Address feedback" git push origin assignment1/issue3
- Create a branch
- Make changes
- Commit your work
- Push to your fork
- Open a pull request
- ❌ Working directly on
main - ❌ Forgetting to push your branch
- ❌ Creating a pull request from the wrong branch
- ❌ Not pulling latest changes before starting work