New Contributing Guide, effective now

[aeppling]

We've published a Contributing Guide that defines how contributions are handled going forward.

What's new

Branch naming is now required

All branches must follow the format type(scope): description:

• fix = patch, feat = minor, chore = major
• scope = the part of the project affected (e.g. git, filter, config)

PR workflow: everything goes through develop

your branch --> develop (review + CI) --> master (versioned release)

PRs must target develop. Maintainers review first, then CI runs. Once stable on develop, changes are released to
master under a specific version.

Please make sure there is no regression before submitting: cargo fmt --all --check && cargo clippy --all-targets &&
cargo test

And test roughly all affected features.

Full details: CONTRIBUTING.md

Transition

PRs opened before this announcement will be reviewed and merged under the previous system. All new PRs from today must
follow the contributing guide.

Questions or feedback? Reply to this thread.