forked from PromtEngineer/localGPT
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0298303
commit 58d7a43
Showing
1 changed file
with
47 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# How to Contribute | ||
|
||
Always happy to get issues identified and pull requests! | ||
|
||
## General considerations | ||
|
||
1. Keep it small. The smaller the change, the more likely we are to accept. | ||
2. Changes that fix a current issue get priority for review. | ||
3. Check out [GitHub guide][submit-a-pr] if you've never created a pull request before. | ||
|
||
## Getting started | ||
|
||
1. Fork the repo | ||
2. Clone your fork | ||
3. Create a branch for your changes | ||
|
||
This last step is very important, don't start developing from master, it'll cause pain if you need to send another change later. | ||
|
||
TIP: If you're working on a GitHub issue, name your branch after the issue number, e.g. `issue-123-<ISSUE-NAME>`. This will help us keep track of what you're working on. If there is not an issue for what you're working on, create one first please. Someone else might be working on the same thing, or we might have a reason for not wanting to do it. | ||
|
||
## Pre-commit | ||
|
||
GitHub Actions is going to run Pre-commit hooks on your PR. If the hooks fail, you will need to fix them before your PR can be merged. It will save you a lot of time if you run the hooks locally before you push your changes. To do that, you need to install pre-commit on your local machine. | ||
|
||
```shell | ||
pip install pre-commit | ||
``` | ||
|
||
Once installed, you need to add the pre-commit hooks to your local repo. | ||
|
||
```shell | ||
pre-commit install | ||
``` | ||
|
||
Now, every time you commit, the hooks will run and check your code. If they fail, you will need to fix them before you can commit. | ||
|
||
If it happened that you committed changes already without having pre-commit hooks and do not want to reset and recommit again, you can run the following command to run the hooks on your local repo. | ||
|
||
```shell | ||
pre-commit run --all-files | ||
``` | ||
|
||
## Help Us Improve This Documentation | ||
|
||
If you find that something is missing or have suggestions for improvements, please submit a PR. | ||
|
||
[submit-a-pr]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request |