From f9df5ab0fe7248cc9194a72f027710eab52609f7 Mon Sep 17 00:00:00 2001 From: George Bartolomey Date: Tue, 17 Sep 2024 11:52:16 +0300 Subject: [PATCH] fixup: Remove unnecessary instructions from CONTRIBUTING.md Signed-off-by: George Bartolomey --- CONTRIBUTING.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 30569c8..5dbd575 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -54,15 +54,6 @@ changes. Maybe you will find it convenient to name branch in $ git checkout -b feature/123-something_awesome ``` -### Test your changes -After your code changes, make sure - -- To add test cases for the new code. -- To run `make lint` and `make staticcheck-run` -- To squash your commits into a single commit or a series of logically separated - commits run `git rebase -i`. It's okay to force update your pull request. -- To run `make test` and `make all` completes. - ### Commit changes After verification, commit your changes. This is a [great post](https://chris.beams.io/posts/git-commit/) on how to write useful commit