This guide assumes you are familiar with several git concepts. If you are not, the list of concepts below also function as links to the documentation for that concept.
The concepts in question are:

• Adding and committing changes
• Working with remotes
  • Pushing changes
  • Pulling changes
• Branching
• Merging

This guide will go through the standard process for making changes to the production repository and some habits you should form when coding.
Note that these are only standards and that the scenarios outlined might not always line up with reality. You might need to take slightly different steps in the event that your situation is some kind of edge case not accounted for here.

Critical Reminders

In general, non-senior developers should NEVER do the following:

• Commit changes to the master branch
• Merge a branch into the master branch
• Commit changes to the dev branch
• Merge a branch into the dev branch
• Open pull requests before merging the dev branch into your feature branch

If you don't understand what some of the above reminders mean, that's ok. They will be reiterated again later in context.

Let's Get Started

Alright, now we can really get going. Go on to the next page to learn how you should begin working on a fresh production repository that you just cloned.