chore: Add CONTRIBUTING.md #438
No reviewers
Labels
No labels
Compat/Breaking
Kind
Bad merge
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
New language
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: mergiraf/mergiraf#438
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "contributing"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It's generally a good practice to have such a file, so let's have one :)
I'm not sure what is worth documenting as I have the impression we follow a fairly standard Rust project structure. Feel free to add things directly with further commits on this branch :)
Maybe add something about the helper scripts? I've yet to to use them myself, and that's at least partially because it seemed like a bit of an effort to understand what they're for^^
@ -0,0 +5,4 @@
### Code style
To format your code, run `cargo fmt`.
This sentence feels a bit lonesome, but I mean we do just use the regular Rust toolset, so it feels a bit redundant to add "lint using
cargo clippy
, test usingcargo test
, build usingcargo build
". OTOH it might be useful for people not familiar with RustLet's delete it for now, people not familiar with Rust are probably mostly people adding support for new languages, and if rustfmt complains on their PRs, it should be easy enough to figure it out for them from the CI logs.
Now that we barely mention the standard cargo commands (only
cargo test
is left), it reads like we use nothing but these shell script helpers, which is not quite representative... But I don't know how much this matters in practice – again, the Rust toolset is uniquely standardized, so we can expect contributors to be aware of all the commands already0599f90717
to8aa384d409