Let’s Add Organization-Wide Issue & PR Templates for ADAMANT

[al-onyxprotocol]

Hey,

To improve consistency across all ADAMANT repositories, I propose we create organization-wide Issue and Pull Request templates.

Templates

GitHub allows us to do this by setting up a special .github repository at the root of our organization.

Inside it, we can place default templates for:
🐞 Bug reports (bug_report.yml)
✨ Feature requests (feature_request.yml)
⚙️ Config (config.yml to control templates and contact links)
🔀 Pull request template (PULL_REQUEST_TEMPLATE.md)

Why this matters

• Provides a clear structure for contributors when reporting bugs or requesting features.
• Ensures important details are not missed (steps to reproduce, motivation, alternatives, etc.).
• Saves time for maintainers by reducing incomplete or unclear issues.
• Improves the overall developer experience across all our projects.

Next steps

1. Create the .github repository in the organization.
2. Add the default templates.
3. Repositories without their own templates will automatically inherit these.

👉 Let’s decide on the final wording/fields for the templates together. Once we agree, I can prepare a PR with ready-to-use files.

What do you think? Should we move forward with this?

[adamant-al]

Yes, this is a great idea and definitely the right direction. 🚀
For example, in the bug report template it’s really important to include clear fields like steps to reproduce and expected vs. actual behavior. That way, issues won’t miss critical details and we can resolve them much faster.

[adamantmm]

Hey,
I've also posted Recommended prefixes for Issue titles #5

[adamantmm]

Pr for templates
#7

[metalisk]

Pr for templates #7

Awaiting for reviewers to merge it.

[adamantmm]

Done!

[al-onyxprotocol]

Useful and templates look good.