docs: add community health files for A+ portfolio standards#8
Conversation
- CONTRIBUTING.md: comprehensive contribution guidelines - SUPPORT.md: clear support channels and response times - CHANGELOG.md: semantic versioning change log template Part of portfolio A+ upgrade initiative.
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Summary
This PR successfully adds community health documentation (SUPPORT.md) as part of the A+ portfolio standards initiative. The file is well-structured with clear sections for different support channels, appropriate response time expectations, and proper references to existing repository files.
Verified:
- ✅ All file references (SECURITY.md, CONTRIBUTING.md, README.md) point to valid files in the repository
- ✅ Markdown syntax is correct
- ✅ Content structure follows GitHub community standards
- ✅ No security vulnerabilities or logic errors
Approval Status: Approved - no blocking issues identified. Safe to merge.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a new SUPPORT.md file outlining how users can get help, report bugs, request features, and contact the maintainers. The review feedback suggests improving the robustness of the links to the repository's issues and discussions by using root-relative paths (e.g., /issues) instead of relative paths (e.g., ../../issues), which can break when viewed from nested branch structures.
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.
| - **Issues**: Check [existing issues](../../issues) - your question may already be answered | ||
| - **Discussions**: Browse [GitHub Discussions](../../discussions) (if enabled) for Q&A and community support |
There was a problem hiding this comment.
The relative links ../../issues and ../../discussions assume a specific directory depth when viewed on GitHub. If this file is viewed on a branch with a slash in its name (e.g., feature/add-support), the URL path has an extra segment, causing these links to resolve to broken URLs (e.g., .../blob/issues or .../blob/feature/issues).
To make these links robust across all branches, tags, and subdirectories, use root-relative paths starting with a /. GitHub automatically resolves links starting with / relative to the repository root.
| - **Issues**: Check [existing issues](../../issues) - your question may already be answered | |
| - **Discussions**: Browse [GitHub Discussions](../../discussions) (if enabled) for Q&A and community support | |
| - **Issues**: Check [existing issues](/issues) - your question may already be answered | |
| - **Discussions**: Browse [GitHub Discussions](/discussions) (if enabled) for Q&A and community support |
There was a problem hiding this comment.
Pull request overview
Adds a community health SUPPORT.md file to document support channels, bug/feature request flow, security reporting guidance, and expected response times.
Changes:
- Introduces
SUPPORT.mdwith links to README, Issues, and (optionally) Discussions. - Documents expectations for bug reports, feature requests, and security vulnerability reporting.
- Defines maintainer contact options and response-time SLAs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **Quick questions**: Open an issue with the `question` label | ||
| - **General discussion**: Use GitHub Discussions (if enabled) or reach out to the maintainer | ||
| - **Community chat**: Check the README for any community Slack/Discord links |
| - **Issues**: Reviewed within 3-5 business days | ||
| - **Pull requests**: Reviewed within 3-5 business days | ||
| - **Security reports**: Acknowledged within 24 hours |
Changes
Context
Part of portfolio A+ upgrade initiative to achieve top 1% GitHub profile standards.
Impact
Docs-only addition, safe to merge.