Issue creation link in the open source docs readme links to the internal docs-content repo

[MoinJulian]

Code of Conduct

• [x] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

This issue is not about the docs.github.com page, but there wasn't a better issue template. In the README of this repository there is a link to create a new issue, points to github/docs-content, which is a private repository, resulting in a 404 for external contributors.

What part(s) of the article would you like to see updated?

As said previously this issue isn't about the docs itself, but I couldn't find a better issue template.

Additional information

No response

[welcome[bot]]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[cceneag]

嗯嗯明白那我選擇延續問題來做發表謝謝

Apple @.***>於 2025年6月4日 週三，上午6:03寫道：

Appletorsh508 left a comment (github/docs#38719) https://github.com/github/docs/issues/38719#issuecomment-2937329755

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct https://github.com/github/docs/blob/main/.github/CODE_OF_CONDUCT.md

What article on docs.github.com is affected?

This issue is not about the docs.github.com page, but there wasn't a better issue template. In the README of this repository there is a link to create a new issue, points to github/docs-content, which is a private repository, resulting in a 404 for external contributors. What part(s) of the article would you like to see updated?

As said previously this issue isn't about the docs itself, but I couldn't find a better issue template. Additional information

No response

— Reply to this email directly, view it on GitHub https://github.com/github/docs/issues/38719#issuecomment-2937329755, or unsubscribe https://github.com/notifications/unsubscribe-auth/BSWC2AQ6EJV22K44QXFYHP33BYLSLAVCNFSM6AAAAAB6QSWZQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMZXGMZDSNZVGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Sharra-writes]

Thanks for opening an issue! That does not sound super helpful, so I will look into that.

[albwo]

1. [](url)

[MoinJulian]

@Sharra-writes can I work on this?

[Sharra-writes]

@MoinJulian I'm so sorry, I keep running into a bug where things don't get added to my project board if I close a tab too fast, and apparently that happened here. I looked into this when it first came up, and you're definitely right about the link, but I'm not sure it can be fixed from the docs repo. The bot doesn't allow contributors to alter certain files, and the README might be one of them (if I'm remembering correctly). You can try opening a PR to see if you get the bot complaining at you about it. In the meantime, I'm going to check and see why this happened in the first place, and I'll update you if there are any nuances to keep in mind.

[Sharra-writes]

@MoinJulian I realized (and then confirmed with my colleague) that the README is actually meant for internal use. That's why we have contributing docs that we link OS contributors to. The docs and docs-internal repos are synced, so they have to be the same. That means that anything in docs-internal meant for internal use is visible to OS contributors.

I am going to talk to my manager about instead updating the language in the README to make it clearer that it's meant for internal use, because right now it absolutely reads like it could be meant for the OS repo. I'm going to close this, but thanks for bringing it to our attention. 💛 Even if the link is okay, the doc as a whole is incredibly confusing and needs some work.