You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -76,19 +79,19 @@ Here we now created a new branch called `devel`. This is the development branch.
76
79
77
80
Now active work is supposed to be done. Therefore a new branch should be created. Let's create one:
78
81
79
-
```
82
+
```sh
80
83
git checkout -b feature/#777
81
84
```
82
85
83
86
There may be many of these feature branches. Most of them are also pushed to the server for discussion or synchronization.
84
87
85
-
```
88
+
```sh
86
89
git push -u origin feature/#777
87
90
```
88
91
89
92
Now feature branches may be closed when they are done. Here we simply merge with the feature branch(es). For instance the following command takes the `feature/#777` branch from the server and merges it with the `devel` branch.
90
93
91
-
```
94
+
```sh
92
95
git checkout devel
93
96
git pull
94
97
git pull origin feature/#777
@@ -97,7 +100,7 @@ git push
97
100
98
101
Finally, we may have all the features that are needed to release a new version of AngleSharp. Here we tag the release. For instance for the 1.0 release we use `v1.0`.
99
102
100
-
```
103
+
```sh
101
104
git checkout master
102
105
git merge devel
103
106
git tag v1.0
@@ -109,7 +112,7 @@ git tag v1.0
109
112
110
113
The following files should not be edited directly in the current repository, but rather in the `AngleSharp.GitBase` repository. They are then synced via `git pull` from a different remote.
0 commit comments