mirror of
https://github.com/go-gitea/gitea.git
synced 2026-08-01 02:30:22 +00:00
7ac32c9b51
Further refinements to AGENTS.md: - consolidate some points - add point about locales - rewrite some points for clarity and size Signed-off-by: silverwind <me@silverwind.io> Co-authored-by: delvh <dev.lh@web.de>
2.1 KiB
2.1 KiB
- Never assume, verify before claiming
- List development targets with
make help - PR descriptions: minimal, only what and why, no task lists or file listings. Include screenshots for UI changes, before and after when modifying existing UI
- Reference issues and PRs by full URL, not by number
- Use Conventional Commits for commit messages and PR titles, plus Gitea's
enhancetype for user-facing enhancements - Add an
Assisted-by: AGENT_NAME:MODEL_VERSIONtrailer to commit messages, neverCo-Authored-ByorSigned-off-by - Attribute agent authorship on one trailing line in issue and PR comments, never as a PR description section
- Never rewrite git history unless asked, update PRs with new commits and normal push
- Comments: write almost none, short and preferably same-line, explaining why for a future reader. Never narrate code, the change or the prompt. Preserve existing ones that still apply
- Add the current year to copyright headers of new
.gofiles - In
options/locale, only editlocale_en-US.json, other locales are synced automatically - In TS, use
!instead of?./??when a value always exists - Prefer
tw-*utilities over inlinestyleandflex-*helpers over per-childtw-ml-*/tw-mr-*margins, falling back totw-*where specificity requires!important - Run
make fmtafter.goedits,make tidyaftergo.modedits,make generate-swaggerafter API changes, and lint what changed withmake lint-go,lint-js,lint-cssorlint-templates - Fix the cause rather than disabling a linter or weakening a test. Where unavoidable, use the narrowest scope with a trailing comment giving the reason
- Run single tests with
go test -run '^TestName$' ./modulepath/for Go,pnpm exec vitest <path-filter>for TS andGITEA_TEST_E2E_FLAGS='<filepath>' make test-e2efor e2e - Write the fewest, fastest tests covering the behavior, extending an existing one where possible. Prefer unit tests where logic is testable in isolation
- Aim for sub-2s per integration test and sub-4s per e2e test. Wait on a deterministic condition rather than
sleep, and prefer semantic locators in e2e tests