-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
GH53958: Fix xref guidelines for contrib doc #65908
Conversation
@bobfuru: No Jira issue with key GH-53958 exists in the tracker at https://issues.redhat.com/. In 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: No Jira issue with key GH-53958 exists in the tracker at https://issues.redhat.com/. In 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: No Jira issue with key GH-53958 exists in the tracker at https://issues.redhat.com/. In 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. |
🤖 Fri Feb 02 16:59:37 - Prow CI generated the docs preview: https://65908--ocpdocs-pr.netlify.app |
@rolfedh can you please review for Hacktoberfest? |
@bergerhoffer It looks you're already engaged in reviewing this one. Please take it from here. |
Hi @bergerhoffer PTAL, not sure if this is what you had in mind for combining to one scenario? Thanks! |
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.
@bobfuru Boy you thought you were picking up an easy one for Hacktoberfest, didn't you? 😉
Anyways, this whole section needs redone. I didn't test it, but I took a stab at rearranging the whole section in this gist: https://gist.github.com/bergerhoffer/a6b8ff4ece7c90ca9105e2ed447142cb
If you want to take that as a starting point / feel free to adjust as you see fit. Thanks again! :)
Thanks for doing the work, @bergerhoffer. I plugged in your gist edits to overwrite cuz they look better than anything I could come up with. Déjà vu! 🤣 |
.... | ||
openshift-docs/ | ||
openshift-docs/foo | ||
openshift-docs/foo/bar.adoc |
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.
Per ISG do not use foo or foobar, as they are "variants of an acronym of a profanity."
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.
Yeah, use /fu/bob
instead! (I'm kidding)
Good to see you @bobfuru! 👋
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.
Good point @mburke5678. We could change these to things like "test1" and "test2" and "example1", "example2", etc.
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.
I substituted foo_bar_baz_zig
variables with test1_test2_test3_example1
variables. But if you have something else in mind, let me know.
Fix xref guidelines for contrib doc, make 1 scenario Fix xref guidelines for contrib doc, make 1 scenario openshiftGH-53958: Fix xref guidelines for contrib doc As called out in the comments: openshift#53958 This updates the `/baz/zig` and `/baz/zag` examples. @openshift/team-documentation PTAL
Sorry for the delay @bobfuru, our GA was today :) I marked this as hacktoberfest-accepted and will come back in the next day or so to finish reviewing! |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
@bergerhoffer Is this PR good to merge? |
/retest |
/remove-lifecycle stale |
@bobfuru: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. In 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-sigs/prow repository. |
As called out in the comments: #53958
This updates the
/baz/zig
and/baz/zag
examples.@openshift/team-documentation PTAL