Updated Octopus Deploy docs #585
Conversation
|
|
||
| Because Octopus uses NuGet under the covers you cannot publish every build into Octopus deploy. For this we have two possible options: | ||
| This limitation means you cannot continue to push revisions in this manner without some intervention (or changes to GitVersion's configuration). To work around this problem we have two possible options: |
There was a problem hiding this comment.
I am not sure that it is right to call this a limitation, I don't think that is the right word.
There was a problem hiding this comment.
How about combining the two like this?
Because Octopus uses NuGet under the covers you cannot continue to push revisions in this manner without some intervention (or changes to GitVersion's configuration). To work around this problem we have two possible options:
|
@sstorie aside from a few small comments, this looks good to me! Thank you very much for your contribution! 👍 |
|
Ok, let me incorporate your suggestions and update the PR. |
|
Ok, I made the updates and the PR appears to have pulled them in. Tanks again for the feedback and let me know if you have any more. |
|
Looks good to me 👍 One final thing though... Are you in a position to flatten these commits into a single commit? i.e. using |
|
I can certainly try...let me see how I do that quick. |
|
This is how we tend to ask people to do it on one of the other projects I work on: |
|
Ok, I'm really struggling with this, so I might just submit a new PR that has the single commit. I made the mistake of making an edit directly on GitHub and I think that's making this much harder for me than it would normally be. |
…marks and an example scenario with the actual git commands.
|
Ok, is this what you are looking for? |
|
Woot! 👍 Much better! |
|
@sstorie thanks again for all your help on this! |
|
No problem. Hopefully it helps the next person :) |
Added some specific git commands and clarified the process for creating Octopus Deploy packages that can be deployed.