You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@texera.apache.org by "Yicong-Huang (via GitHub)" <gi...@apache.org> on 2026/08/07 23:19:19 UTC
[I] Document PR title conventions for feat vs fix, tests, dependency bumps, and backports [texera]
Yicong-Huang opened a new issue, #7393:
URL: https://github.com/apache/texera/issues/7393
### Task Summary
Our contribution docs say PR titles follow Conventional Commits, but never say how to pick the type or scope. Five cases get decided ad hoc: `feat` vs `fix`, what counts as a `refactor`, test-only PRs, dependency bumps, and backport versions.
Write the rule down across the contributor guide, the docs site page, the agent guide, and the pull request template. Behavior that worked before and no longer does is a `fix`. Adding, removing, or reworking a functionality is a `feat`. A change guaranteed to leave observable behavior unchanged is a `refactor`. A test-only PR is a test change; repairing a broken test is a fix in test code. A dependency bump is a fix only when it patches a CVE. A release-branch PR carries the version as the last scope component.
### Task Type
- [x] Documentation
--
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: notifications-unsubscribe@texera.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Document PR title conventions for feat vs fix, tests, dependency bumps, and backports [texera]
Posted by "Yicong-Huang (via GitHub)" <gi...@apache.org>.
Yicong-Huang closed issue #7393: Document PR title conventions for feat vs fix, tests, dependency bumps, and backports
URL: https://github.com/apache/texera/issues/7393
--
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: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org