Yicong-Huang opened a new pull request, #7427:
URL: https://github.com/apache/texera/pull/7427
### What changes were proposed in this PR?
`CONTRIBUTING.md` requires Conventional Commits for PR titles but never says
how to pick the type or scope, so recurring cases get decided ad hoc. This
writes the convention down:
- **Type follows the behavior**, not the diff size:
- worked before, broken now → `fix`
- adding, removing, or reworking a functionality → `feat`
- guaranteed to leave observable behavior unchanged → `refactor`, which
must keep the existing tests passing untouched
- **Tests**: a test-only PR is `test(<module>)`; repairing a broken or flaky
test is `fix(test, <module>)`.
- **Dependencies**: `fix(deps, <module>)` when the bump patches a CVE,
`chore(deps, <module>)` otherwise, `ci:` for CI-only bumps.
- **Backports**: a release-branch PR appends the version as the last scope
component, e.g. `fix(deps, frontend, v1.2): ...`.
One behavior change worth flagging. `backport-auto-label.yml` auto-labels
only `fix(...)` PRs. The CVE/non-CVE split therefore narrows auto-backporting
to security bumps, where the old runtime-vs-toolchain split sent every runtime
bump there.
### Any related issues, documentation, discussions?
Closes #7393
### How was this PR tested?
- Documentation only — no code path changes.
- Verified the new title forms pass the CI type gate and the review-time
title check, both on `main` and with a version scope on `release/v1.2`.
- Confirmed `direct-backport-push.yml`'s rewriter already emits the
documented backport form, so no workflow change is needed.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 5)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
