|
| 1 | +<!-- PR template generated from CONTRIBUTING.md. Modify as needed. --> |
| 2 | + |
| 3 | +# Title |
| 4 | + |
| 5 | +Use Conventional Commits style for the PR title (recommended): |
| 6 | + |
| 7 | +```text |
| 8 | +<type>(<scope>): <short description> |
| 9 | +``` |
| 10 | + |
| 11 | +Example: `feat(api): add OpenRouter fallback handler` |
| 12 | + |
| 13 | +--- |
| 14 | + |
| 15 | +## Description |
| 16 | + |
| 17 | +Please include a summary of the change and which issue is fixed. Also include relevant motivation and context. |
| 18 | + |
| 19 | +- What does this change do? |
| 20 | +- Why is this change needed? |
| 21 | +- Any notable implementation details? |
| 22 | + |
| 23 | +If this is a large change, consider splitting into smaller PRs. |
| 24 | + |
| 25 | +## Related issue |
| 26 | + |
| 27 | +Fixes: #ISSUE_NUMBER (if applicable) |
| 28 | + |
| 29 | +## Checklist (required) |
| 30 | + |
| 31 | +Please check the items that apply before requesting review: |
| 32 | + |
| 33 | +- [ ] The branch name follows the project's convention (e.g. `dev/...`) |
| 34 | +- [ ] The PR title follows Conventional Commits |
| 35 | +- [ ] Linting passes locally: `bun run lint` |
| 36 | +- [ ] Type checking passes: `bun run typecheck` |
| 37 | +- [ ] Build succeeds: `bun run build` |
| 38 | +- [ ] Tests added/updated for new behavior (if applicable) |
| 39 | +- [ ] Updated changelog or release notes (if applicable) |
| 40 | +- [ ] I have linked related issues and provided a clear description |
| 41 | +- [ ] Screenshots, recordings, or example outputs are included for UI/UX changes |
| 42 | +- [ ] No secrets or credentials are committed in this PR |
| 43 | + |
| 44 | +## How to test |
| 45 | + |
| 46 | +Provide clear instructions for how reviewers can reproduce and verify the changes locally (commands, env vars, fixtures): |
| 47 | + |
| 48 | +```bash |
| 49 | +# example |
| 50 | +bun install |
| 51 | +bun run build |
| 52 | +bun run typecheck |
| 53 | +# run tests |
| 54 | +bun test |
| 55 | +``` |
| 56 | + |
| 57 | +## Security & Private Data |
| 58 | + |
| 59 | +If this PR addresses a security vulnerability, do NOT include exploit details here. Follow the repository's `SECURITY.md` instructions for private disclosure. |
| 60 | + |
| 61 | +## Additional notes |
| 62 | + |
| 63 | +Add any other context for the reviewer (migration steps, configuration changes, limitations, backwards-incompatible changes). |
| 64 | + |
| 65 | +--- |
| 66 | + |
| 67 | +Terima kasih telah mengirimkan PR — kami akan meninjaunya sesegera mungkin. |
0 commit comments