Skip to content

Commit 819efcb

Browse files
committed
Updated docs to make clearer
1 parent 848aad8 commit 819efcb

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/configuration.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -249,15 +249,15 @@ Because git is a directed graph GitVersion sometimes cannot tell which branch th
249249
Take this graph
250250

251251
```
252-
* feature/foo
253-
* | release/1.0.0
252+
* release/1.0.0 * feature/foo
253+
| ________________/
254254
|/
255255
*
256256
*
257257
* (master)
258258
```
259259

260-
By looking at this graph, you cannot tell which of these scenarios happened
260+
By looking at this graph, you cannot tell which of these scenarios happened:
261261

262262
1. feature/foo branches off release/1.0.0
263263
- Branch release/1.0.0 from master
@@ -271,6 +271,8 @@ By looking at this graph, you cannot tell which of these scenarios happened
271271
- Add a commit to both release/1.0.0 and feature/foo
272272
- feature/foo is the base for release/1.0.0
273273

274+
Or put more simply, what branch was created first, `release/1.0.0` or `feature/foo`.
275+
274276
To resolve this issue we give GitVersion a hint to how we normally do our branching, feature branches have a value of:
275277

276278
`sourceBranches: ['master', 'develop', 'feature', 'hotfix', 'support']`

0 commit comments

Comments
 (0)