summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAmjith Ramanujam <amjith.r@gmail.com>2023-05-03 10:10:20 -0700
committerGitHub <noreply@github.com>2023-05-03 10:10:20 -0700
commit6cc4773aaaaafe7b013b3e15e8828979253ed49a (patch)
treed958d83439c23c59894bd1e7b24ba9dd6d9a4759
parent536e29dcb53062184da72c4e93541192ad26ca7d (diff)
parent8cac55323d9879fdf795c5a66957524aba2e416f (diff)
Merge pull request #159 from bjornasm/patch-1
Update CONTRIBUTING.md
-rw-r--r--CONTRIBUTING.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9cd868a..a38d8d2 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -49,7 +49,7 @@ You'll always get credit for your work.
$ pip install --editable .
```
-6. Create a branch for your bugfix or feature based off the `master` branch:
+6. Create a branch for your bugfix or feature based off the `main` branch:
```bash
$ git checkout -b <name-of-bugfix-or-feature>
@@ -58,7 +58,7 @@ You'll always get credit for your work.
7. While you work on your bugfix or feature, be sure to pull the latest changes from `upstream`. This ensures that your local codebase is up-to-date:
```bash
- $ git pull upstream master
+ $ git pull upstream main
```
8. When your work is ready for the litecli team to review it, push your branch to your fork: