Fix callout numbering#22794
Conversation
|
The preview will be available shortly at: |
bobfuru
force-pushed
the
fix-callout-numbering
branch
from
26ca528 to
855b430
Compare
|
@bobfuru, there is this fix: Didn't realize it was possible, but an SME had it in a contributed PR. |
|
@bobfuru, would love to learn of a clean solution, though. |
@jboxman I've used this before but couldn't get it to work in this case, which has an admonition note within two callout descriptions. It's also inside of a numbered step, though not sure that should matter. I ended up just making the note part of <1>. By coincidence, I think it improved readability. |
bobfuru
added
the
peer-review-done
|
/cherrypick enterprise-4.5 |
|
/cherrypick enterprise-4.4 |
|
@bobfuru: new pull request created: #22795 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@bobfuru: new pull request created: #22796 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
4 participants
Relates to this PR 22785 and this comment:
#22785 (comment)
@bmcelvee Unfortunately, when I add the continuing
+, it doesn't continue the callout numbering. (Instead, it lists both callouts as #1.) I couldn't figure out a better workaround, and ultimately reverted back to original formatting. I actually think I mucked with this when the original content was created. Will continue to investigate a fix for this.