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: docs/contributing/index.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,17 @@ Hey, thanks for considering to contribute!
5
5
If you did this before you probably know the gist, but check out this little guide to get everything set-up!
6
6
7
7
## Setup environment for code/docs changes
8
-
1. Install [Poetry](https://python-poetry.org/docs/#installation) for project managment, it is like pip but better and feature-richer. You can work on this project without it, but I highly recommend not to do this.
8
+
1. Install [Poetry](https://python-poetry.org/docs/#installation) for project management, it is like pip but better and feature-richer. You can work on this project without it, but I highly recommend not to do this.
9
9
2. Clone: `git clone https://github.com/sdaqo/anipy-cli && cd anipy-cli`
10
10
3. Initiate your environment: `poetry install --with dev,docs`, this installs all the dependencies and some development tools.
11
11
4. (Optional) If you are working on the API and you want to be able to test your changes in the cli, you can run `poetry run poe enter-dev`. (this changes the api dependency to the local `../api`)
12
-
5. Open your edior, you can either run `poetry run <your-editor>` or `poetry shell` to get a shell in the virtual environment and run your editor from there, some editors like vscode automatically enter the venv as far as I know.
12
+
5. Open your editor, you can either run `poetry run <your-editor>` or `poetry shell` to get a shell in the virtual environment and run your editor from there, some editors like vscode automatically enter the venv as far as I know.
13
13
6. Make your changes :)
14
14
7. Check your changes
15
15
- Run `poetry run anipy-cli` to run the cli.
16
16
- Run `poetry run python` to run python from the virtual environment.
17
17
- Run `poetry run poe docs-serve` to open host the docs locally, this is helpful if you are making changes to the docs.
18
-
8. Run `poetry run poe polish` before commiting to format and lint your code. The linter will tell you what you did wrong, fix that if you think the suggestion from the linter is reasonable, if not don't bother. Also, please do not concern yourself with linter errors that you did not introduce!
18
+
8. Run `poetry run poe polish` before committing to format and lint your code. The linter will tell you what you did wrong, fix that if you think the suggestion from the linter is reasonable, if not don't bother. Also, please do not concern yourself with linter errors that you did not introduce!
19
19
9. Run `poetry run poe exit-dev` if you ran the command in step 4.
20
20
10. Push & Pull Request!
21
21
@@ -24,11 +24,11 @@ If you did this before you probably know the gist, but check out this little gui
0 commit comments