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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganize the CI (attempt #2) #1084
Reorganize the CI (attempt #2) #1084
Changes from all commits
419baf7
c7f719f
6f471df
db40fc9
bcbd4a1
4ff864e
520e9fa
8788d2b
7566571
a71f336
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can add a:
With a
needs
onpublish
and aon.workflow_call
oncontinuous-integration.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would make sense to have
publish
step executed only when the tests pass, but isn't the current version fine? I.e. the maintainer should not release a new version until all the CI jobs pass, right?Also what is the meaning of
secrets
? I have not tried yet the trusted publishing approach, but I thought that it would not use secrets anymore?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, for the most part it is ok. Adding a dependency like that will make sure that if there were any upstream changes in the meantime, everything is still good. I usually run
ci-build-wheel
only before release because of how thorough it is andtest
just for good measure.secrets
is not really necessary there. It basically makes sure that your secrets (inpublish
) propagate tocontinous-integration.yml
. Since these are within the same project and there are no special secret treatments, it can be dropped.