chore: add contributor templates (PTC-25) - #138
Conversation
Added a feature request template for GitHub issues with fields for problem description, proposed solution, affected area, and alternatives considered.
Added a pull request template to guide contributors.
There was a problem hiding this comment.
Code Review
This pull request introduces GitHub issue templates for bug reports and feature requests, a configuration file for issue templates, and a pull request template to standardize contributions. The reviewer suggested keeping blank issues enabled in the configuration to reduce friction for early contributors who might want to submit issues that do not fit the structured templates.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Added a contributing section to encourage community involvement. (at the bottom)
|
Defer to 1.11 due to missed review deadline |
Co-authored-by: Stephen (DB Tycoon) <stephen@databasetycoon.com>
Co-authored-by: Stephen (DB Tycoon) <stephen@databasetycoon.com>
Part of PTC-25. Adds the baseline contributor templates:
.github/ISSUE_TEMPLATE/)One thing to flag for review: I set
blank_issues_enabled: falsein config.yml, so people have to use the bug/feature forms or head to Discussions — no freeform blank issues. It keeps the Issues tab clean and matches the engagement-first push. But it's a bit opinionated for where we are, and there's a case for leaving blank issues on so an early contributor with an odd report isn't blocked by the forms. Happy either way — flag it if you'd rather I flip it to true before merge.Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.