doc: fix typo in --require-hash and add detail #471
Merged
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
1085f6d to
b2e79aa
Compare
|
@mikemccracken sign the commit pls |
--require-flag was a typo take the opportunity to add some extra detail and be clear about what happens with that flag. Signed-off-by: Michael McCracken <mikmccra@cisco.com>
b2e79aa to
d0aa600
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.
--require-flag was a typo
take the opportunity to add some extra detail and be clear about what happens with that flag.
What type of PR is this?
This is a documentation PR
Which issue does this PR fix:
No issue was filed.
What does this PR do / Why do we need it:
fixes an error in the docs
If an issue # is not available please add repro steps and logs showing the issue:
see https://stackerbuild.io/v0.40.1/reference/stacker_file/?h=hash#import-hash
Testing done on this change:
no testing, yolo
Automation added to e2e:
see above re: yolo
Will this break upgrades or downgrades?
Let's hope not
Does this PR introduce any user-facing change?:
Not during usage.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
👍