generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 89
Update call-out shortcode usage in Contributing #286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
2b9ecbb
to
c7ba758
Compare
✅ Deploy Preview will be available once build job completes!
|
mjang
reviewed
Mar 13, 2025
mjang
approved these changes
Mar 13, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with one suggested change
Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com>
JTorreG
approved these changes
Mar 13, 2025
travisamartin
pushed a commit
that referenced
this pull request
Mar 13, 2025
* chore: Update call-out shortcode usage in Contributing * Update with suggestion Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com> --------- Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com>
travisamartin
added a commit
that referenced
this pull request
Mar 19, 2025
…#287) * Removed unnecessary metadata keys and standardized the remaining ones * Update call-out shortcode usage in Contributing (#286) * chore: Update call-out shortcode usage in Contributing * Update with suggestion Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com> --------- Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com> * removed extra blank line after front matter block * edits * Update content/controller/admin-guides/install/resilient-cluster-aws.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> * Update content/mesh/about/mesh-tech-specs.md * fixed types that had blank values * removed null from empty descriptions * removed ' character from weight key * removed trial links that weren't correct --------- Co-authored-by: Lam <150060045+lamATnginx@users.noreply.github.com> Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com> Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> Co-authored-by: Alan Dooley <a.dooley@f5.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
process documentation
Documentation related to how the repository or documention itself is managed.
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.
Proposed changes
Update
CONTRIBUTING_DOCS.md
for new usage ofcall-out
shortcode. See below for output:Before:

After:

Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.md
andCHANGELOG.md
Footnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩