making issue templates organization wide, as discussed in Discord

[kpj2006]

• Evaluate org-wide .github templates
• Migrate common templates to org scope
• Keep repo-level overrides only where necessary
• Deprecate local templates after migration

Follow-up tracked in issue #3 .

[Aarya-Chaudhari]

Hi @kpj2006

I’d like to take this issue up if it’s okay.
Plan is to:

1. Audit existing issue templates across repositories
2. Identify common templates suitable for org-wide usage
3. Create organization-level templates in the .github repository
4. Update a sample repo to use the org-level templates
5. Document the migration and deprecation approach

I’ll share progress updates here before opening a PR.
Please let me know if this plan aligns with expectations.

[kpj2006]

Hi @Aarya-Chaudhari,

A small clarification before we proceed: this discussion is specifically about using .github repo which is not exist yet(as discussed on Discord). wait for @Zahnentferner to create it.

During that i except from you:

Finalize the org-level .github repo architecture by visiting popular org repo

Do a bit more research and consensus-building on how org-wide templates vs repo-level overrides should work
(e.g. ISSUE_TEMPLATE )

main concern is about existing repositories:
The intent is not to force-migrate or break old repos. Repo-level templates can remain as overrides.

Appreciate your willingness to take this up!!

[Aarya-Chaudhari]

Okay
I will wait till the creation of .GitHub repo and until then I will research as told by you and will update it over here.
Thanks