mirror of
https://github.com/snapotter-hq/SnapOtter.git
synced 2026-08-03 07:46:42 +02:00
SnapOtter
fa50266ea4
- 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
1.0 KiB
1.0 KiB
What does this PR do?
Fixes #
Type of change
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- New translation or i18n update
- Documentation update
- Test improvement
- Refactor (no functional change)
Checklist
- I have read CONTRIBUTING.md
- I have signed the CLA (the bot will prompt you if not)
- My changes follow the project's code style (Biome passes)
- I have added or updated tests for my changes
- All existing tests pass locally (
pnpm test) - TypeScript compiles without errors (
pnpm typecheck) - My PR is focused on a single concern (under 400 lines of change)
- I have not modified CI, release, or linter configuration files