forked from bazel-contrib/rules_python
-
Notifications
You must be signed in to change notification settings - Fork 1
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: AugustKarlstedt/rules_python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: alexrudy/rules_python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 619 files changed
- 2 contributors
Commits on May 25, 2023
-
fix: respect kind mapping (bazel-contrib#1158)
When using the kind `gazelle:map_kind` directive, `gazelle` will correctly generate the buildfile on the first pass (or if no target of that type / name are present). However, when running gazelle a second time (or if a target of the mapped kind with the same name is present), `gazelle` will error out saying that it kind create a target of the original kind because a target of mapped kind is present and has the same name. Ex: Given the directive `# gazelle:map_kind py_test py_pytest_test //src/bazel/rules/python:py_pytest_test.bzl`, `gazelle` will correctly generate a `py_pytest_test` target where it would have generated a `py_test` target. But on a second invocation of `gazelle` (and subsequent invocations) it will error our with: ``` gazelle: ERROR: failed to generate target "//test/python/common:common_test" of kind "py_test": a target of kind "py_pytest_test" with the same name already exists. Use the '# gazelle:python_test_naming_convention' directive to change the naming convention. ```
Configuration menu - View commit details
-
Copy full SHA for 1eea0a9 - Browse repository at this point
Copy the full SHA 1eea0a9View commit details -
Configuration menu - View commit details
-
Copy full SHA for df919d7 - Browse repository at this point
Copy the full SHA df919d7View commit details -
Configuration menu - View commit details
-
Copy full SHA for adeec04 - Browse repository at this point
Copy the full SHA adeec04View commit details -
Configuration menu - View commit details
-
Copy full SHA for e9648e2 - Browse repository at this point
Copy the full SHA e9648e2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 71eb8dd - Browse repository at this point
Copy the full SHA 71eb8ddView commit details -
Configuration menu - View commit details
-
Copy full SHA for 05efdfc - Browse repository at this point
Copy the full SHA 05efdfcView commit details -
Configuration menu - View commit details
-
Copy full SHA for b07ae7c - Browse repository at this point
Copy the full SHA b07ae7cView commit details
Commits on May 26, 2023
-
Configuration menu - View commit details
-
Copy full SHA for cc27e41 - Browse repository at this point
Copy the full SHA cc27e41View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...main