Here are all of the steps you should follow whenever contributing to this repo!
- Before you start making changes, always make sure you're on the
developbranch, thengit fetchto retrieve all new remote branches, and finallygit pull. If you have local uncommitted changes,git stash, thengit pull --rebaseto get latest from origin, thengit stash popto apply the stashed changes to new base. - Don't forget to
npm iin the/frontendandpoetry installin the/backendto make sure your dependencies are up to date. In the/backend, for each new terminal session, you'll also have to runpoetry shellto reactive your virtual environment. - Create a new branch by first checking out develop with
git checkout developorgit switch develop. Then, rungit checkout -b <name-of-branch>. - Make changes to the code. If it's been a while since you've made changes, repeat Steps 1 and 2.
- If you need to add dependencies in the backend, run
poetry add package-name, orpoetry update package-nameto update a dependency. - Run the project locally to ensure everything is still working properly with
chalice localin the backend, andnpm run devin the frontend. npm run lintto ensure code standards. (runningnpm run lint:fixwill fix most of the styling errors!)
When interacting with Git/GitHub, feel free to use the command line, VSCode extension, or Github Desktop. These steps assume you have already made a branch using git checkout -b <branch-name> and you have made all neccessary code changes for the provided task.
- View diffs of each file you changed using the VSCode Github extension (3rd icon on far left bar of VSCode) or GitHub Desktop
git add .(to stage all files) orgit add <file-name>(to stage specific file)git commit -m "<type>[optional scope]: <description>"orgit commit -m "<type>[optional scope]: <description>" -m "[optional body]"git push -u origin <name-of-branch>
- Go to the Pull Requests tab on github.com
- Find your PR, fill out the PR template (can also be found in
.github/directory) - (If applicable, provide a screenshot of your work in the comment area)
- Link your PR to the corresponding Issue
- Request a reviewer to check your code (either
ryanchansforoli-lane) - Once approved, your code is ready to be merged in (TLs will merge and close all PRs)🎉