Skip to content

Commit 65e4695

Browse files
committed
Merge pull request #800 from dcorriveau-omniscient/DocVersionIncrementFixTypo
Fixed "packages" typo in the version-increment doc page
2 parents 43a3ab6 + ee452c7 commit 65e4695

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/more-info/version-increments.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ There are a few ways to handle this problem depending on what your requirements
1414
### 1. GitFlow
1515
If you are using GitFlow then builds off the `develop` branch will actually *increment on every commit*. This is known in GitVersion as *continuous deployment mode*. By default `develop` builds are tagged with the `unstable` pre-release tag. This is so they are sorted higher than release branches.
1616

17-
If you need to consume packages built from develop, we recommend publishing these packages to a separate NuGet feed as an alpha channel. That way you can publish beta/release candidate builds and only people who opt into the alpha feed will see the unstable pacakges.
17+
If you need to consume packages built from develop, we recommend publishing these packages to a separate NuGet feed as an alpha channel. That way you can publish beta/release candidate builds and only people who opt into the alpha feed will see the unstable packages.
1818

1919
### 2. Octopus deploy
2020
See [Octopus deploy](../build-server-support/build-server/octopus-deploy.md)

0 commit comments

Comments
 (0)