-
Notifications
You must be signed in to change notification settings - Fork 185
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: TheKevJames/coveralls-python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 2.2.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: TheKevJames/coveralls-python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.0.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 5 files changed
- 3 contributors
Commits on Jan 12, 2021
-
docs(github): fixes env var flag details (#244)
Details: * The docs section 'Github Actions Gotcha' stated that the COVERALLS_FLAG_NAME env var is needed in order to avoid 'pile up of jobs'. It turns out that it is optional, and when specified, can be specified with the same value across all jobs or with unique values. This change clarifies that in the documentation. * This change also clarifies that the COVERALLS_REPO_TOKEN env var is not needed for GitHub Actions. * This change also renames the heading of the section to 'Github Actions support' to have a more neutral name. Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
Configuration menu - View commit details
-
Copy full SHA for 14cea5a - Browse repository at this point
Copy the full SHA 14cea5aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 05b66aa - Browse repository at this point
Copy the full SHA 05b66aaView commit details -
Configuration menu - View commit details
-
Copy full SHA for db523ff - Browse repository at this point
Copy the full SHA db523ffView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6ebdc5e - Browse repository at this point
Copy the full SHA 6ebdc5eView commit details -
feat(config): reorder configuration precedence (#249)
We've been getting a slew of cases where users are reporting requiring different configurations -- especially Github Actions, where we seem to need to set a different service name on a case-by-case basis. Reordering our configuration precedence such that user-specified values overwrite the CI defaults should allow users to fix these problems without requiring a one-size-fits-all code change. This is massively backwards incompatible for anyone with the same key set to two different values in their configs.
Configuration menu - View commit details
-
Copy full SHA for f4faa92 - Browse repository at this point
Copy the full SHA f4faa92View commit details -
Configuration menu - View commit details
-
Copy full SHA for 209a13a - Browse repository at this point
Copy the full SHA 209a13aView 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 2.2.0...3.0.0