-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[NO-QA]Use renamed git repo for change step #7409
Conversation
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 see it here: umani/changed-files@1d252c6 |
Weird, I see the same commit with a different hash: |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @roryabraham in version: 1.1.33-4 🚀
|
🚀 Deployed to production by @sketchydroide in version: 1.1.34-0 🚀
|
Details
futuratrepadeira/changed-files
was renamed toumani/changed-files
, I'm not sure it's causing errors in this repo, but it was in a different one, so let's just update to the renamed repo just in case.Tests
updateProtectedBranch.yml
continues to check for the correct files changed