Skip to content

docs: contributing guideline#4347

Merged
aldy505 merged 4 commits into
masterfrom
aldy505/docs/contribution
May 30, 2026
Merged

docs: contributing guideline#4347
aldy505 merged 4 commits into
masterfrom
aldy505/docs/contribution

Conversation

@aldy505
Copy link
Copy Markdown
Collaborator

@aldy505 aldy505 commented May 23, 2026

No description provided.

@aldy505 aldy505 marked this pull request as ready for review May 23, 2026 08:12
@aldy505 aldy505 requested review from BYK and hubertdeng123 May 23, 2026 08:12
Comment thread CONTRIBUTING.md
Copy link
Copy Markdown
Collaborator

@aminvakil aminvakil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Except .env.custom all are nitpicking really.

Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Generated and managed config files live in the repo working tree:

- `.env` is the default environment file.
- `.env.custom` is loaded automatically when present and should be your normal place for local overrides.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not get picked up by docker compose automatically, you should use something like this for it to get passed to containers:

docker compose --env-file .env --env-file .env.custom up --wait

Copy link
Copy Markdown
Collaborator

@aminvakil aminvakil May 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should get changed before merging.

Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md
- Call out any generated files, config migrations, or operator-visible behavior changes.
- Include the exact validation you ran locally.
- Link upstream issues or PRs when the root cause is outside this repository.
- Keep commit history readable. A small number of focused commits is better than a long stream of fixups.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to add "Take it easy though, focus on your development instead of commits" somehow, but I cannot think of a good sentence.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by "instead of commits"?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never mind, it's not really important, I just wanted to tell users to take it easy, shift your focus to your development and really fixing the bug, or perfecting the feature you're adding, rather than breaking your commits into good one change / one commit, good commit messages, ...

That would be great if commits are tidy as well, but that's not as important as code change itself.

Overall I think current sentence of yours is correct, users are not going to hurt themselves after reading this :)

@aldy505 aldy505 requested a review from aminvakil May 28, 2026 07:32
Copy link
Copy Markdown
Member

@BYK BYK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work, thanks!

@aldy505 aldy505 merged commit 54d47c7 into master May 30, 2026
20 checks passed
@aldy505 aldy505 deleted the aldy505/docs/contribution branch May 30, 2026 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants