Lines Matching +full:pre +full:- +full:commit +full:- +full:config

18 gh repo fork bazelbuild/rules_python --clone --remote
23 [install pyenv](https://github.com/pyenv/pyenv-installer) and
39 git checkout -b my-feature # Create and switch to our feature branch
40 git push origin my-feature # Cause the branch to be created in your fork.
43 From here, you then edit code and commit to your local branch. If you want to
47 git push origin my-feature
66 the tests in those directories instead, which can speed up your edit-run cycle.
70 It's suggested to routinely update the tool versions within our repo - some of the
72 to have everything self-documented, we have a special target -
82 We suggest using a pre-commit hook to automate this.
83 First [install pre-commit](https://pre-commit.com/#installation),
87 pre-commit install
97 $ buildifier --lint=fix --warnings=native-py -warnings=all WORKSPACE
120 [GitHub Help]: https://help.github.com/articles/about-pull-requests/
122 ### Commit messages
124 Commit messages (upon merging) and PR messages should follow the [Conventional
137 the [Breaking Changes](#breaking-changes) section for how to introduce breaking
144 * `feat:` means a user-visible feature is being added.
145 * `fix:` means a user-visible behavior is being fixed.
146 * `refactor:` means some sort of code cleanup that doesn't change user-visible behavior.
155 Some checked-in files are generated and need to be updated when a new PR is
176 - Anything concerning the way Bazel implements the core Python rules should be
178   the label `team-Rules-python`.
180 - If the issue specifically concerns the rules_python stubs, it should be filed
181   here in this repository and use the label `core-rules`.
183 - Anything else, such as feature requests not related to existing core rules
185   `core-rules` label.
187 (breaking-changes)=
190 Breaking changes are generally permitted, but we follow a 3-step process for
221   `@rules_python_internal//:config.bzl` file.
223   behavior is likely to vary on a per-target basis.
224 * [User defined build settings](https://bazel.build/extending/config#user-defined-build-settings)
226   generally wouldn't vary on a per-target basis. They also have the benefit that
249 how load-bearing it has become and what sort of reasonable expectation of
267 ### Installation errors when during `git commit`
269 If you did `pre-commit install`, various tools are run when you do `git commit`.