Fake Pull Request for Test Purposes #942
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically synchronised from an OctopusDeploy internal git repository using Copybara.
Adding a Release Note
Any change to the OctopusClients code must have a release note.
Only changes that are internal-only (for example adding some unit tests) should not have release notes.
To add a Release Note, Add a comment to this pull request with the text "Release Note: <your text here>"
Semantic Versioning
You must check exactly one of these options:
How to Merge this PR
Add a comment with the text "/merge". An automated process will merge the PR.
This will fail if there are no release notes, as release notes are generally required.
Add a comment with the text "/merge norelease" to merge without release notes for internal-only changes.
Merging this way will not release the change (No package will be published to NuGet)