gavindiaz/awesome-quant
1
0
Fork 0
mirror of https://github.com/wilsonfreitas/awesome-quant.git synced 2026-08-22 00:08:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: align PR reviews with commercial policy

Browse Source
This commit is contained in:
Wilson Freitas
2026-08-16 09:41:28 -03:00
parent 73a4bc4127
commit 6f79dbc83d
3 changed files with 52 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+14 -6
View File
@@ -64,10 +64,14 @@ Rules:
- Each tag must use its own backtick pair, for example `` `Python` `C++` `MCP` ``.
- Descriptions must end with a period before the optional `[GitHub](...)` link.
- URLs in new entries must use `https://`.
- A valid GitHub repository used as the main URL or exact `[GitHub](...)` suffix is a strong
positive relevance signal. Review its activity and documentation rather than treating
non-language tags as format errors.
- Commercial/proprietary projects belong in `## Commercial & Proprietary Services`.
- A valid GitHub repository used as the main URL or exact `[GitHub](...)` suffix is preferred
and is a strong positive relevance signal, but it is not universally required. Functional-
section placement requires a repository containing substantive implementation; a thin SDK,
integration, examples, generated-data, or marketing repository does not qualify.
- Hosted commercial/proprietary products without substantive public source belong in
`## Commercial & Proprietary Services`, even when a thin repository exists. Repository-less
services qualify only under the permanent free tier and transparency rules in
`CONTRIBUTING.md`.
- Backtick tags are optional only for commercial services and other metadata-free
sections such as `Related Lists`.
- Use `CONTRIBUTING.md` as the user-facing source for contribution rules.
@@ -89,8 +93,12 @@ Review requirements:
4. Always ask the user before commenting, labeling, closing, or merging.
5. Check section placement, duplicates in `README.md`, entry format, URL format,
and project activity/documentation. Give substantial positive weight to a verifiable
GitHub repository mentioned as either the main URL or exact suffix.
6. Use the `reviewed` label only after the user approves a review comment.
GitHub repository mentioned as either the main URL or exact suffix, while confirming that
functional-section repositories contain substantive implementation.
6. Manually assess commercial entries for free-tier usefulness, payment information,
public pricing and limits, public documentation/methodology/examples, stable non-tracking
URLs, concise factual description tone, and repository substance.
7. Use the `reviewed` label only after the user approves a review comment.
## GitHub MCP Tools