TheZwiss
6c7cbee808
The CLA Assistant only records a signature when the exact phrase is posted as a comment on the PR, so ticking the checkbox alone left the check red with no explanation (see #39). Spell the required comment out next to the checkbox, using the exact phrase from custom-pr-sign-comment in .github/workflows/cla.yml.
31 lines
1.2 KiB
Markdown
31 lines
1.2 KiB
Markdown
<!-- Thanks for contributing. Keep one logical change per pull request. -->
|
|
|
|
## What this changes
|
|
|
|
<!-- A short summary of the change and the problem it solves. Link the issue it addresses. -->
|
|
|
|
Closes #
|
|
|
|
## Type of change
|
|
|
|
- [ ] Bug fix
|
|
- [ ] New feature
|
|
- [ ] Refactor or cleanup
|
|
- [ ] Documentation
|
|
- [ ] Other
|
|
|
|
## Checklist
|
|
|
|
- [ ] `pnpm build` succeeds (shared types, server, and web all build)
|
|
- [ ] `pnpm dev` starts the server and web client without errors
|
|
- [ ] Tests pass where applicable (`pnpm test`)
|
|
- [ ] I updated the relevant `docs/systems/` spec if this changed schema, API routes, WebSocket events, the federation protocol, permissions, or the design system
|
|
- [ ] This change resolves the correct federated identity where it compares IDs, checks permissions, or talks to remote servers (no assumption of a single global user ID)
|
|
- [ ] I have read and agree to the [CLA](../CLA.md) — ticking this box is not the
|
|
signature. After opening this PR, post a separate comment containing exactly:
|
|
`I have read the CLA Document and I hereby sign the CLA`
|
|
|
|
## Notes for reviewers
|
|
|
|
<!-- Anything that helps review: screenshots for UI, migration notes, edge cases, follow-ups. -->
|