Skip to content

CONTRIBUTING: Clarify some constraints for PR submission.#1134

Open
agatti wants to merge 1 commit into
micropython:masterfrom
agatti:commit-guidelines-update
Open

CONTRIBUTING: Clarify some constraints for PR submission.#1134
agatti wants to merge 1 commit into
micropython:masterfrom
agatti:commit-guidelines-update

Conversation

@agatti

@agatti agatti commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR updates the contribution guidelines to clarify some points related to submitting PRs in a way that wouldn't fail basic CI checks.

The contribution guidelines assumed that all PRs would come from a properly set-up environment, which it may not always be the case for small changes being done from within GitHub itself. However these PRs would not undergo the checks provided by the pre-commit hooks that are set up in a properly set-up environment.

These changes aim to dissuade users who read the guidelines first to submit PRs from GitHub directly but to do so from a configured environment, and if that is not the case to at least make explicit the commit message validation criteria. There isn't much to do for code formatting rules besides saying to use "ruff" first, unfortunately.

This PR was inspired by the brief discussion in #1077 - not to single the PR out - as the guidelines weren't clear on certain points and we end up with a PR that, whilst it fixed an existing issue, cannot be merged for reasons that may not be explicit enough.

Generative AI

I did not use generative AI tools when creating this PR.

@agatti agatti added the docs label Jul 3, 2026
This commit updates the contribution guidelines to clarify some points
related to submitting PRs in a way that wouldn't fail basic CI checks.

The contribution guidelines assumed that all PRs would come from a
properly set-up environment, which it may not always be the case for
small changes being done from within GitHub itself.  However these PRs
would not undergo the checks provided by the pre-commit hooks that are
set up in a properly set-up environment.

These changes aim to dissuade users who read the guidelines first to
submit PRs from GitHub directly but to do so from a configured
environment, and if that is not the case to at least make explicit the
commit message validation criteria.  There isn't much to do for code
formatting rules besides saying to use "ruff" first, unfortunately.

Signed-off-by: Alessandro Gatti <a.gatti@frob.it>
@agatti agatti force-pushed the commit-guidelines-update branch from 915a6ec to c1512dd Compare July 3, 2026 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant