CI: FORCE_COLOR for readable tox/pytest outputs, use OIDC PyPI uploads #1282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1282 +/- ##
=======================================
Coverage 92.24% 92.24%
=======================================
Files 99 99
Lines 12460 12460
Branches 2561 2561
=======================================
Hits 11494 11494
Misses 643 643
Partials 323 323 ☔ View full report in Codecov by Sentry. |
effigies
force-pushed
the
ci/oidc-and-color
branch
from
107a24d
to
7efda1b
Compare
effigies
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two small cleanups for the CI run. One is to enable colored tox output for improved readability.
The other is to enable trusted publishing so that releases from this repository can be uploaded without relying on a maintainer having an active token scoped to the project in the repo secrets. We have a "Package deployment" environment that waits on a maintainer to approve upload.