Mindmap
2.4.5 Describe the GitHub Workflow
Inhalt der Mindmap
2.4.5 Describe the GitHub Workflow
We need to establish a good GitHub workflow so that when we make changes locally, we also update our remote GitHub repo so that everything stays in sync
A branch is a copy or version of the code that can be worked on independtly in isolation so development changes do not disrupt other team members who are also working on the code and testing their solutions
- Default branch is called main or master
- No coding directly in the main branch
- Branch off of main and create a feature branch, a copy of the main branch
- In the feature branch, we make commits of all the changes we make to the code while working
- We add a commit message that is descriptive of what changed in the code
- Developers commit often!
- Push up the changes to our feature branch in our GitHub repository
- In order to merge our changes to the main branch we need to open a pull request
- A pull request or PR is used to merge a comparison branch (feature branch) into the base brance
- The base branch is where the changes will be merged into - the default branch main
- PR needs to be approved prior to merging
- The base branch is where the changes will be merged into - the default branch main
- A pull request or PR is used to merge a comparison branch (feature branch) into the base brance
- In order to merge our changes to the main branch we need to open a pull request
- We add a commit message that is descriptive of what changed in the code
- In the feature branch, we make commits of all the changes we make to the code while working
- Branch off of main and create a feature branch, a copy of the main branch
- No coding directly in the main branch
- Default branch is called main or master
Informationen
- Beschreibung
- Mindmap am 2.4.5 Describe the GitHub Workflow, erstellt von Frankie Balvert am 11/10/2022.
- Erstellt von
- Frankie Balvert · Okt 2022
- Aktualisiert
- 11 Okt 2022
- Aufrufe
- 0
- Bewertung