vitae/backend-vitae
5
0
Fork 1
Code Issues 5 Pull requests 1 Projects 1 Releases Packages Wiki Activity Actions

Starting the contribution guide in the documentation #15

Merged
Riverfount merged 2 commits from chore/docs into main 2025-10-11 15:34:40 -03:00
Conversation 4 Commits 2 Files changed 5 +142 -10
dunossauro commented 2025-10-09 22:28:19 -03:00
Member
Copy link

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.
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
Author
Member
Copy link

related #6

related #6
Riverfount requested changes 2025-10-10 07:27:47 -03:00
Dismissed
Riverfount left a comment
Owner
Copy link

I just commented — please respond and then proceed.

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)!
Riverfount commented 2025-10-10 07:25:50 -03:00
Owner
Copy link

@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?
dunossauro commented 2025-10-10 15:50:36 -03:00
Author
Member
Copy link

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…

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…
Riverfount commented 2025-10-10 16:18:04 -03:00
Owner
Copy link

Okay, I understand. Let's keep it this way!

Okay, I understand. Let's keep it this way!
Riverfount marked this conversation as resolved
dunossauro commented 2025-10-10 15:53:19 -03:00
Author
Member
Copy link

Regarding the whole, any further changes? Especially concerning the contribution text.

Regarding the whole, any further changes? Especially concerning the contribution text.
Riverfount approved these changes 2025-10-10 16:19:01 -03:00
Riverfount left a comment
Owner
Copy link

Looks good to me!

Looks good to me!
Riverfount deleted branch chore/docs 2025-10-11 15:34:40 -03:00
Sign in to join this conversation.
Reviewers
No reviewers
Riverfount
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: vitae/backend-vitae#15
No description provided.
Delete branch "chore/docs"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?