You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,24 +1,23 @@
1
1
# Pull requests (for contributors)
2
2
3
3
- Test your changes:
4
-
- 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
4
+
- 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
5
5
- Execute [the full CI locally on your machine](ci/README.md) before publishing
6
-
- Please 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.
7
-
- The PR template has a series of review complexity checkboxes `[ ]` that [you can mark as](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists)`[X]` for your convenience
8
-
- Consider allowing write access to your branch for faster review
6
+
- 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
7
+
- Consider allowing write access to your branch for faster reviews, as reviewers can push commits directly
9
8
- If your PR becomes stale, don't hesitate to ping the maintainers in the comments
10
9
11
10
# Pull requests (for collaborators)
12
11
13
12
- Squash-merge PRs
14
13
- Use the following format for the squashed commit title: `<module> : <commit title> (#<issue_number>)`. For example: `utils : fix typo in utils.py (#1234)`
15
-
- Optionally, pick a `<module>` from here: https://github.com/ggerganov/llama.cpp/wiki/Modules
14
+
- Optionally pick a `<module>` from here: https://github.com/ggerganov/llama.cpp/wiki/Modules
16
15
17
16
# Coding guidelines
18
17
19
18
- Avoid adding third-party dependencies, extra files, extra headers, etc.
20
19
- Always consider cross-compatibility with other operating systems and architectures
21
-
- Avoid fancylooking modern STL constructs, use basic `for` loops, avoid templates, keep it simple
20
+
- Avoid fancy-looking modern STL constructs, use basic `for` loops, avoid templates, keep it simple
22
21
- There are no strict rules for the code style, but try to follow the patterns in the code (indentation, spaces, etc.). Vertical alignment makes things more readable and easier to batch edit
23
22
- Clean-up any trailing whitespaces, use 4 spaces for indentation, brackets on the same line, `void * ptr`, `int & a`
24
23
- Naming usually optimizes for common prefix (see https://github.com/ggerganov/ggml/pull/302#discussion_r1243240963)
0 commit comments