From 7ba63fec82aed1558b547dd0c75bef70deb4e5b5 Mon Sep 17 00:00:00 2001 From: "Tobin C. Harding" Date: Wed, 6 Mar 2024 08:53:14 +1100 Subject: [PATCH 1/2] Fix typo --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b1ae86c3..f2c5c598 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -78,7 +78,7 @@ To contribute a patch, the workflow is a as follows: 2. Create topic branch 3. Commit patches -Please keep commits should atomic and diffs easy to read. For this reason +Please keep commits atomic and diffs easy to read. For this reason do not mix any formatting fixes or code moves with actual code changes. Further, each commit, individually, should compile and pass tests, in order to ensure git bisect and other automated tools function properly. From 41f0a802aff231fbaa7f2f49b8af63f0c7d897bf Mon Sep 17 00:00:00 2001 From: "Tobin C. Harding" Date: Wed, 6 Mar 2024 08:53:29 +1100 Subject: [PATCH 2/2] Remove assigned docs We don't assign issues, remove the incorrect section. --- CONTRIBUTING.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f2c5c598..7cb1a33d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -91,12 +91,6 @@ to split it into multiple small, focused PRs. Commits should cover both the issue fixed and the solution's rationale. Please keep these [guidelines](https://chris.beams.io/posts/git-commit/) in mind. -To facilitate communication with other contributors, the project is making use -of GitHub's "assignee" field. First check that no one is assigned and then -comment suggesting that you're working on it. If someone is already assigned, -don't hesitate to ask if the assigned party or previous commenters are still -working on it if it has been awhile. - ## Preparing PRs