Jaymr/new-api
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
new-api/.github/PULL_REQUEST_TEMPLATE/en.md
T
Seefs e468b73915 docs: update PR template and remove PR Check workflow (#7053) 
* docs: update PR template and remove PR Check workflow

* docs: add hidden agent issue and PR templates
2026-08-27 22:36:44 +08:00

2.6 KiB
Raw Permalink Blame History

PR Notice

Chinese template: .github/PULL_REQUEST_TEMPLATE.md

Important

  • AI-assisted descriptions are welcome. Please review the full text before submitting and take responsibility for it. Avoid pasting unreviewed content.
  • Please complete this template before submitting.

Related Issue

  • For new features, please fill in the Issue number below. If none exists yet, please create one first. Please discuss the feature in the Issue rather than using the PR in its place.

  • For large or directional changes, please reach agreement with maintainers in the linked Issue before opening a PR.

  • Bug fixes should link a corresponding Issue. Design trade-offs, misunderstandings, or mismatched expectations are a better fit for a discussion or feature request.

  • Closes #

Type of change

  • Bug fix
  • New feature
  • Performance / Refactor
  • Documentation

Description

(Briefly describe what changed and why it works. If that is hard to summarize, consider splitting the scope or aligning with maintainers in an Issue first.)

Proof of Work

(Please describe how this was verified: the steps run and what was observed. For UI changes, please include a screenshot or recording. For bug fixes, please describe the reproduction and the result after the fix.)

Checklist

  • Human review: Whether or not the description was AI-generated, I have reviewed the full content and take responsibility for its accuracy and completeness.
  • Not a duplicate: I have searched existing Issues and PRs and confirmed this is not a duplicate.
  • Feature issue: If this PR is a New feature, I have linked a corresponding Issue; if none existed, I created one first.
  • Prior discussion: If this is a large or directional change, I have discussed it with maintainers in the linked Issue and reached agreement.
  • Scope: This PR is not a Coding Plan, reverse-engineered channel, third-party API wrapper, or a change to the Codex channel type.
  • Focused change: This PR is a single focused change and does not include unrelated code.
  • Local verification: I have run tests or manually verified locally so maintainers can re-check from this evidence.
  • Security: This change does not include secrets and follows the project's coding guidelines.
Reference in New Issue View Git Blame Copy Permalink