Add additional curl example for environment prefixes #508
Conversation
This file contains 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
|
Dear @DLeich, thanks for the PR! This is Vox Pupuli Tasks, your friendly Vox Pupuli Github Bot. I noticed that your pull request has CI failures. Can you please have a look at the failing CI jobs? |
ghoneycutt
approved these changes
Mar 5, 2021
bastelfreak
approved these changes
Mar 5, 2021
bastelfreak
force-pushed
the
webhook_curl_prefixes
branch
from
eb6a855
to
f1ee0fc
Compare
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.
Pull Request (PR) description
The current documentation for triggering the webhook via curl only specifies an example for non-prefixed environments. With the current data structure format, it's unclear whether the full environment name needs to be specified in the 'ref' parameter. This PR implements clear documentation, noting that the full environment name is required.
This Pull Request (PR) contributes a partial fix for the following issues
#422