fix: address review issues in contribution infrastructure

- CODEOWNERS: use @snapotter-hq username instead of non-existent team
- PR template: use absolute URLs (relative links break in PR body)
- CLA: strengthen entity definition with successor/assignee clause
- CLA workflow: store signatures on dedicated branch, add owner to allowlist
- CONTRIBUTING: clarify approval means the "approved" label, reword CCLA
- Bug template: allow "running from source" for developer contributors
This commit is contained in:
SnapOtter
2026-05-16 16:08:16 +08:00
parent 29d959e7c1
commit fa50266ea4
6 changed files with 21 additions and 21 deletions
+3 -3
View File
@@ -19,8 +19,8 @@ We accept pull requests for:
| New translations | Open a PR directly (see [Translation Guide](https://docs.snapotter.com/guide/translations)) |
| Documentation improvements | Open a PR directly |
| Test coverage improvements | Open a PR directly |
| New tools or features | Open an issue first, wait for approval before writing code |
| Refactors or architecture changes | Open an issue first, wait for approval before writing code |
| New tools or features | Open an issue first, wait for a maintainer to add the `approved` label before writing code |
| Refactors or architecture changes | Open an issue first, wait for a maintainer to add the `approved` label before writing code |
### What We Will Not Accept
@@ -38,7 +38,7 @@ Before we can merge your first PR, you must sign our [Individual CLA](CLA.md). T
**How:** When you open your first PR, the CLA Assistant bot will comment with a link. Click it, review the agreement, and sign with your GitHub account. Takes 30 seconds.
If you are contributing on behalf of your employer, your employer must sign the Corporate CLA. Contact contact@snapotter.com for details.
If you are contributing on behalf of your employer and your employer retains IP rights over your work, contact contact@snapotter.com to arrange a Corporate CLA before submitting.
## Development Setup