-
Notifications
You must be signed in to change notification settings - Fork 0
Pull Requests
Cody Ley-Han edited this page Mar 26, 2018
·
1 revision
Having standardized PRs are important, thus we will use the following style.
- Start with type of PR ie feat, bug, tech, style
- In parenthesis say what portion of the app you changed ie auth, core, rides, etc
- A short description of what the PR is for
Example:
feat(auth): Pulls user data from google oAuth
We will also have a standard body with the following format
# Description
This allows for a more detailed explanation of everything in the PR, images are good to have also
# Steps to Reproduce
The steps that someone needs to do to verify the PR is correct
# Tested
Talk about what tests were written, and if there needs to be more testing
# Approved
Who needs to approve the PR before being merged