Skip to content

Commit 9ca4c3e

Browse files
committed
Trying to make docs a bit clearer
1 parent 7db7e8f commit 9ca4c3e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/configuration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -273,11 +273,11 @@ By looking at this graph, you cannot tell which of these scenarios happened:
273273

274274
Or put more simply, what branch was created first, `release/1.0.0` or `feature/foo`.
275275

276-
To resolve this issue we give GitVersion a hint to how we normally do our branching, feature branches have a value of:
276+
To resolve this issue, we give GitVersion a hint to our branching workflows by telling it what types of branches it can be created from. For example feature branches are by default configured to have the following source branches:
277277

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

280-
This means that we will never bother to evaluate pull requests as merge base options, being explicit like this helps GitVersion be much faster too.
280+
This means that we will never bother to evaluate pull request branches as merge base options, being explicit like this helps GitVersion be much faster too.
281281

282282
### is-source-branch-for
283283
The reverse of the above setting. This property was introduced to keep it easy to extend GitVersion's config.

0 commit comments

Comments
 (0)