summaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2023-12-10 10:18:43 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2023-12-10 10:18:43 +0000
commit44ba8147bbb1b651867b4b04e1711273d4a7281c (patch)
treed8c169e12006bfa46e436a180fd531aaac08aad5 /CONTRIBUTING.md
parentAdding upstream version 1.9.0. (diff)
downloadlitecli-44ba8147bbb1b651867b4b04e1711273d4a7281c.tar.xz
litecli-44ba8147bbb1b651867b4b04e1711273d4a7281c.zip
Adding upstream version 1.10.0.upstream/1.10.0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-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: