The list used in this course is opinionated, we should add a remark stating this.
⌨️ Activity: Create a pull request for the remark
Check out master branch.
Create a branch named bugfix-remark.
Add the remark text at the bottom of ci.md.
> **GitHub flow** is sometimes used as a nickname to refer to a flavor of trunk-based development
when code is deployed straight from feature branches. This list is just an interpretation
that I use in my [DevOps courses](http://redpill.solutions).
The official tutorial is [here](https://guides.github.com/introduction/flow/).
Commit the changes.
Push branch bugfix-remark to the remote.
Open a pull request named Adding a remark with head branch bugfix-remark and base branch master.
Show the commands...
```bash
# Check out master branch. Create a branch named bugfix-remark.
git checkout master
# Create a branch named bugfix-remark.
git checkout -b bugfix-remark
# Add the remark text at the bottom of ci.md.
# Commit the changes
git add ci.md
git commit -m "Add remark about the list being opinionated"
# Push branch bugfix-remark to the remote.
git push --set-upstream origin bugfix-remark
# Open a pull request using GitHub UI as described above
```
Add remark about the CI steps being opinionated
The list used in this course is opinionated, we should add a remark stating this.
⌨️ Activity: Create a pull request for the remark
master
branch.bugfix-remark
.ci.md
.bugfix-remark
to the remote.bugfix-remark
and base branchmaster
.Show the commands...
```bash # Check out master branch. Create a branch named bugfix-remark. git checkout master # Create a branch named bugfix-remark. git checkout -b bugfix-remark # Add the remark text at the bottom of ci.md. # Commit the changes git add ci.md git commit -m "Add remark about the list being opinionated" # Push branch bugfix-remark to the remote. git push --set-upstream origin bugfix-remark # Open a pull request using GitHub UI as described above ```