We utilize Conventional Commits for our commit messages. This helps maintain the semantic versioning of this module.
Please use the following commit types: build, chore, ci, docs,
feat, fix, perf, refactor, revert, style, test.
For PRs with changes entirely within a single sub-package, please use
a scope that references that package such as arrow/flight or
parquet/pqarrow. For more general PRs, a top level scope should be
sufficient.
For example:
fix(arrow/cdata): handle empty structs in C data interface
ci: update CI environment
feat(parquet): support new encoding type
The Arrow project uses GitHub as a bug tracker. To report a bug, sign in to your GitHub account, navigate to GitHub issues and click on New issue .
To be assigned to an issue, add a comment "take" to that issue.
Before you create a new bug entry, we recommend you first search among existing Arrow issues in GitHub.
If there is a corresponding issue for your patch, please make sure to reference the issue in your PR description.
We ask that all discussions about major changes in the codebase happen publicly on the arrow-dev mailing-list.
You can also ask on the mailing-list, see above.
Please read our development documentation or look through the New Contributor's Guide.