Starting the contribution guide in the documentation #15

dunossauro · 2025-10-09T22:28:19-03:00

dunossauro commented

2025-10-09 22:28:19 -03:00

In this commit, the contribution page was added, the mkdocs-exec was included to ensure that taskipy is always up to date, and the helps for taskipy were also added.

In this commit, the contribution page was added, the `mkdocs-exec` was included to ensure that taskipy is always up to date, and the helps for `taskipy` were also added.

dunossauro added 1 commit

2025-10-09 22:28:20 -03:00

Starting the contribution guide in the documentation 79fae17a89

In this commit, the contribution page was added, the `mkdocs-exec` was included to ensure that taskipy is always up to date, and the helps for `taskipy` were also added.

dunossauro commented

2025-10-09 22:31:13 -03:00

related #6

dunossauro added 1 commit

2025-10-09 22:33:03 -03:00

fix unicode chars on docs dfa2a91c35

Riverfount requested changes

2025-10-10 07:27:47 -03:00

Dismissed

Riverfount left a comment

I just commented — please respond and then proceed.

docs/contrib.md

					
				@ -0,0 +34,4 @@

				This project uses [`uv`](https://docs.astral.sh/uv/) as the project manager, and you can perform operations through it.

				```bash

				uv venv #(1)!

@dunossauro This command is unnecessary because the first time you run uv sync, it creates the virtual environment automatically.

What do you think?

@dunossauro This command is unnecessary because the first time you run `uv sync`, it creates the virtual environment automatically. What do you think?

We can remove it, no problem. But I had some problems with that. When changing branches with different pyprojects versions (like in one with docs and another without docs), I need to recreate venv many times…