Skip to content

Commit 4a492d1

Browse files
committed
Use markdown numbered list in githubflow.md
1 parent eeede0c commit 4a492d1

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/git-branching-strategies/githubflow.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,12 @@ GitHub Flow is a simple and effective branching strategy which the folks at GitH
33

44
GitHub Flow is in a nutshell:
55

6-
1) Update master to latest [upstream](../reference/git-setup.md#upstream) code
7-
2) Create a feature branch `git checkout -b myFeatureBranch`
8-
3) Do the feature/work
9-
4) Push feature branch to [origin](../reference/git-setup.md#origin)
10-
5) Create pull request from origin/<featureBranch> -> upstream/master
11-
6) Review, fix raised comments, merge your PR or even better, get someone else to.
6+
1. Update master to latest [upstream](../reference/git-setup.md#upstream) code
7+
1. Create a feature branch `git checkout -b myFeatureBranch`
8+
1. Do the feature/work
9+
1. Push feature branch to [origin](../reference/git-setup.md#origin)
10+
1. Create pull request from origin/<featureBranch> -> upstream/master
11+
1. Review, fix raised comments, merge your PR or even better, get someone else to.
1212

1313
The main rule of GitHub Flow is that master should *always* be deployable. GitHub Flow allows and encourages [continuous delivery](../reference/continuous-delivery.md).
1414

0 commit comments

Comments
 (0)