Fix analyze step stuck with no code changes#264
Merged
jezdez merged 1 commit intoconda:mainfrom Mar 2, 2026
Merged
Conversation
danyeaw
force-pushed
the
fix-analyze-step
branch
from
e2f3c6c to
b6e2c9b
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
I noticed that PRs #260 and #262 were stuck on the analyze step. We were filtering on paths to not rerun all the tests, but then the analyze step was getting stuck. This PR uses the solution from the conda repo to filter changes using the dorny/paths-filter action. This will allow the analyze run to see the other jobs passed as allowed-skips.
Checklist - did you ...
Add a file to thenewsdirectory (using the template) for the next release's release notes?Add / update necessary tests?Add / update outdated documentation?