-
Notifications
You must be signed in to change notification settings - Fork 0
Initial cleanup #8
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
|
The following access changes will be introduced as a result of applying the plan: Access Changes |
|
@galargh : I'm sorry to pull you in but I'm unclear how this PR has gotten into a bad state. I did the sync workflow and reran all the steps. Do you have any pointers? I look forward to learning so I can be more self-sufficient in the future. |
d182e8c to
898190f
Compare
|
Before merge, verify that all the following plans are correct. They will be applied as-is after the merge. Terraform plansFilOzone |
898190f to
dff1382
Compare
|
So, the plan was failing because we were removing a repository in this PR (bfc7383, https://github.com/FilOzone/github-mgmt/actions/runs/15454450995/job/43503796496). Removing a repository is not a permitted operation in GitHub as Code because it is hard/impossible to revert cleanly. The sync that you run removed that repository from the config on the default branch (1fc8f23) but since we also touched that repository, the PR couldn't be cleanly updated. The fix was to manually merge the default branch into this PR and resolve the conflicts. In this case, the conflict resolution was to accept the repository removals from the default branch. Now, all the workflows are passing again and the PR can be cleanly merged 🥳 |
Summary
Why do you need this?
What else do we need to know?
DRI: myself
Reviewer's Checklist