Conversation
Moving the scripts under .github left report.yml inserting 'scripts' on sys.path, so the render step died with ModuleNotFoundError and no comment or label was ever posted. The gate itself was unaffected, analyze.yml still ran and still decided pass or fail, but every pull request kept whatever label it had from the run before. Verified by running the render step against the report from the jodit pull request: errors=0, warnings=1, and the comment renders.
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
1 participant
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.
report.ymlstill insertedscriptsonsys.pathafter the machinery moved under.github, so its render step failed with:The gate was never affected —
analyze.ymlran, decided pass or fail, and uploaded its report. What broke is the half that reports it: no comment was posted and no label was applied, so a pull request kept whatever label the previous run left. That is why #1 shows a green check and a staleneeds-changes.Caught by run 35495537365 on #1.
Verified by running the render step's exact snippet against the report artifact from that pull request:
errors=0,warnings=1, comment renders.Also corrects the regeneration command in
.github/rules/reserved.json, stale from the same move.