docs: sync the substitutions chapter with the stacker file article #52
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
mbshields
changed the title
mbshields
changed the title
|
Why is the commit message style still failing? At first, there was no space after the colon, but now I've edited it to add a space. |
rchincha
approved these changes
Apr 11, 2024
mbshields
force-pushed
the
docs_mishield_substitutions
branch
from
fb32210
to
d9d950a
Compare
Signed-off-by: mbshields <[email protected]>
mbshields
force-pushed
the
docs_mishield_substitutions
branch
from
d9d950a
to
010874b
Compare
|
Git issues. It was quicker to just make a new PR (#54 ) |
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.
The substitution sections of these two files are now updated and in sync with each other. There is redundancy, but these two documents are likely to be arrived at from different circumstances -- one is part of the user guide and the other is a reference. This should address Issue #51