- 
                Notifications
    You must be signed in to change notification settings 
- Fork 7.2k
Remove viable strict workflow #8676
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
Conversation
| 🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/8676
 Note: Links to docs will display an error until the docs builds have been completed. ❌ 7 New Failures, 1 Unrelated FailureAs of commit 9c6d14e with merge base f0ed07d ( NEW FAILURES - The following jobs have failed:
 
 BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures 
 
 This comment was automatically generated by Dr. CI and updates every 15 minutes. | 
I discovered that you don't actually have to check out the test-infra repository because it's already there? Docs: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#default-environment-variables Only available for composite actions unfortunately Testing: https://github.com/pytorch/pytorch/actions/runs/11225822033?pr=137454 (actual pushing is commented out) There are also two fetch_latest_green_commit.py scripts in test-infra so I merged them and chose the location in tools/scripts. The logic between the two is pretty much the same. gitutils was copied from .github/scripts (but we don't need much of it) There's also a reusable workflow update-viablestrict and a composite action update-viablestrict. The composite action is usually used, but there are some differences between the two, and vision uses the reusable workflow so I can't get rid of it just yet. (idk how much they care tho, I don't vision has succeeded updating viable/strict in a while). I also can't just make the reusable action call the composite action since the workflow uses an ssh key to check out but the action uses a token --- If pytorch/vision#8676 gets merged, I'll remove the reusable workflow
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.
Trusting you on this @clee2000
| Hey @NicolasHug! You merged this PR, but no labels were added. | 
Only used in pytorch/vision, which was removed in pytorch/vision#8676 The composite action version still exists
Reviewed By: vmoens Differential Revision: D68021981 fbshipit-source-id: 41fb238fc098c76a4ddd4c76cf49bda37bb93ce6
The branch hasn't been updated in 8 months, and it's using a weird version of the viable strict update that I want to get rid of