Open maxwelldb opened 1 year ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle rotten
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Thanks for reporting this issue, @maxwelldb. Could you provide a reference to the "xref guidelines in this repo"? I'm evaluating issues for hacktoberfest and this information would help.
Pulling from my Slack history, as it's been a while:
The example here should actually start
xref:../baz/zag...
@rolfedh
Thanks, Max! You didn't have to do that! I need help finding the document you made a screenshot of. Can you give me a link?
Oh! Yep. :)
Screenshot of error is from: https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#links-to-internal-content
@bobfuru :wave: can you comment on this issue so that we can assign it to you?
@maxwelldb should these sections actually be combined? Afaik there isn't any difference in how an xref is contructed depending on whether the assembly is in the same directory or not.
If that's true, then it seems like we should get rid of "two scenarios" deal and just cut it down to here's how you xref.
Sounds copacetic.
Hi @bergerhoffer! 👋 Please assign this to me. Many thanks!
@bobfuru Let me know if you'd be up for adjusting the xref guidelines like I recommended above. There really is no difference in the xref guidance depending on where you are linking to.
Hi @bergerhoffer. I was out on Friday. It looks like you've got this one.
@bobfuru Let me know if you'd be up for adjusting the xref guidelines like I recommended above. There really is no difference in the xref guidance depending on where you are linking to.
Sure, added a change to the PR. Let me know what you think.
While working on https://issues.redhat.com/browse/OCPBUGS-4982, I realized that the xref guidelines in this repo are incorrect.
Ex: assemblies in the same directory are not linked to as demonstrated.
The xref guidelines should be fixed and verified.