Skip to content
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

"Could not load digger config" Error on PRs #1656

Closed
noralutz opened this issue Aug 12, 2024 · 1 comment · Fixed by #1659
Closed

"Could not load digger config" Error on PRs #1656

noralutz opened this issue Aug 12, 2024 · 1 comment · Fixed by #1659
Assignees

Comments

@noralutz
Copy link

noralutz commented Aug 12, 2024

Recently upgraded both the Digger backend and Workflow runner from version 0.4.6 to vLatest (0.6.20 at that time) and immediately started receiving this comment on all PRs post-merge:

❌ Could not load digger config, error:
Checking the backend, this error appears to not be new, and was happening pre-update, but was potentially swallowed and not commented. This occurs on all PRs closed in the repo, even ones that do not affect any terraform code, so it is quite disturbing to developers who do not know why this message appears.

Notably, on the backend I see these errors corresponding to branches that the PR recently closed and deleted:

PlainClone error: couldn't find remote ref "refs/heads/branch_name"
github.go:682: Error cloning and loading config: couldn't find remote ref "refs/heads/branch_name"

I assume this is some issue with the Digger backend attempting to check out the branch upon PR merge, but we automatically delete branches on PR merge, so they will always be deleted. Could this be related to #1155?

@noralutz
Copy link
Author

@motatoes tagging as requested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants