From e8f2a2dac12d91544306c1ca0ad3645d90c21c9b Mon Sep 17 00:00:00 2001 From: Georgi Gerganov Date: Sat, 30 Nov 2024 09:50:54 +0200 Subject: [PATCH] contrib : refresh --- .github/pull_request_template.md | 4 ---- CONTRIBUTING.md | 3 +-- 2 files changed, 1 insertion(+), 6 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 997c6d9d0..f6603098e 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,7 +1,3 @@ - [x] I have read the [contributing guidelines](https://github.com/ggerganov/llama.cpp/blob/master/CONTRIBUTING.md) -- Self-reported review complexity: - - [ ] Low - - [ ] Medium - - [ ] High diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4c882c254..32da00a8c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,9 +1,8 @@ # Pull requests (for contributors) - Test your changes: - - Using the commands in the [`tests`](tests) folder. For instance, running the `./tests/test-backend-ops` command tests different backend implementations of the `ggml` library + - Run the `test-backend-ops` tool to validate different backend implementations of the `ggml` operators - Execute [the full CI locally on your machine](ci/README.md) before publishing -- Optionally rate the complexity of your PR (i.e. `Review Complexity : Low`, `Review Complexity : Medium`, `Review Complexity : High`). This makes it easier for maintainers to triage the PRs - Consider allowing write access to your branch for faster reviews, as reviewers can push commits directly - If your PR becomes stale, don't hesitate to ping the maintainers in the comments