CONTRIBUTING: merge STYLE into contents #168

Open
emma wants to merge 2 commits from contributing-style-merge into main
Owner
No description provided.
emma added the
enhancement
label 2025-04-03 16:48:31 -06:00
emma self-assigned this 2025-04-03 16:48:32 -06:00
emma added 2 commits 2025-04-03 16:48:34 -06:00
emma requested review from trinity 2025-04-03 16:49:10 -06:00
emma requested review from silt 2025-04-03 16:49:17 -06:00
Owner

i don't agree with the decision to merge these two documents. it is true that they're related, but they present distinct enough information (and exist at different enough stages of the development process) to warrant keeping them separate.

i don't agree with the decision to merge these two documents. it is true that they're related, but they present distinct enough information (and exist at different enough stages of the development process) to warrant keeping them separate.
Author
Owner

@silt: where is the line between CONTRIBUTING and STYLE?

@silt: where is the line between CONTRIBUTING and STYLE?
Owner

the latter concerns itself with matters of code formatting and convention, and the former everything else

the latter concerns itself with matters of code formatting and convention, and the former everything else
trinity reviewed 2025-04-05 06:37:14 -06:00
trinity left a comment
Owner

Looks good to me. I agree with this change.

Looks good to me. I agree with this change.
Owner

I think style falls under the CONTRIBUTING umbrella nicely; it's one little handbook that tells you how to participate in the project, from the forest to the trees.

I think style falls under the `CONTRIBUTING` umbrella nicely; it's one little handbook that tells you how to participate in the project, from the forest to the trees.
This pull request can be merged automatically.
You are not authorized to merge this pull request.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin contributing-style-merge:contributing-style-merge
git checkout contributing-style-merge
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bonsai/harakit#168
No description provided.