You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using @renovatebot to manage my dependencies and our GitHub Action got upgraded from 2.1.14 to 2.1.16 in UCL-MIRSG/.github@78f2369. At this point, the workflow began failing.
It looks like it is going through every repo and trying to rename it to terraform-harvester-modules. It then errors because https://github.com/UCL-MIRSG/terraform-harvester-modules already exists. I have no idea why is this happening, or why that particular repo was selected. For now I have downgraded to 2.1.14.
I'll attach the full logs in a comment underneath.
What is the expected behavior
The upgrading version shouldn't have broken the workflow.
Problem Description
What is actually happening
I am using @renovatebot to manage my dependencies and our GitHub Action got upgraded from
2.1.14
to2.1.16
in UCL-MIRSG/.github@78f2369. At this point, the workflow began failing.It looks like it is going through every repo and trying to rename it to
terraform-harvester-modules
. It then errors because https://github.com/UCL-MIRSG/terraform-harvester-modules already exists. I have no idea why is this happening, or why that particular repo was selected. For now I have downgraded to2.1.14
.I'll attach the full logs in a comment underneath.
What is the expected behavior
The upgrading version shouldn't have broken the workflow.
Error output, if available
The relevant bit of the log is
Context
Are you using the hosted instance of probot/settings or running your own?
Running in GitHub Actions.
If running your own instance, are you using it with github.com or GitHub Enterprise?
Version of probot/settings
Version of GitHub Enterprise
The text was updated successfully, but these errors were encountered: