Closed leomp12 closed 4 years ago
Does the branch renovate/docker-digests-pin exist on GitHub already? Do you have any git pre-commit checks?
@leomp12 dependencyDashboard
can be helpful for you too. You can manually trigger a run from the dependencyDashboard issue. Maybe it was a transient git push error.
Seems likely that pin branch error is blocking other branches, the question is why the push is failing.
Hey guys, thanks for the quick response!
@rarkins no renovate/docker-digests-pin
branch, not even any renovate/*
branch, and only master
and v*-dev
are protected. We have pre-commit check for commit msg with husky here.
@viceice I've tried dependecyDashboard
here, manually triggered request but still getting the same problem.
Not sure if Dependency Dashboard is working as expected, it says:
These updates are awaiting their schedule. Click on a checkbox to ignore the schedule.
But I've checked chore(deps): pin calibreapp/github-image-actions docker tag
, then triggered new Renovate request manually and it stills trying to update calibreapp/github-image-actions
:thinking:
My best guess is that the husky pre-commit check is failing, although I'm not sure why.
@rarkins I think the problem is happening with calibreapp/github-image-actions
(GH Actions) only, so I've tried to ignore it from the Dependency Dashboard issue, but Renovate stills trying to update it and we're getting the same error.
Logs from 2 hours ago:
...
DEBUG: Writing any updated package files(branch="renovate/docker-digests-pin")
DEBUG: No updated lock files in branch(branch="renovate/docker-digests-pin")
DEBUG: 1 file(s) to commit(branch="renovate/docker-digests-pin")
DEBUG: Committing files to branch renovate/docker-digests-pin(branch="renovate/docker-digests-pin")
DEBUG: Error commiting files(branch="renovate/docker-digests-pin")
{
"err": {
"task": {
"commands": [
"push",
"origin",
"renovate/docker-digests-pin:renovate/docker-digests-pin",
"--force",
"-u",
"--no-verify",
"--verbose",
"--porcelain"
],
"format": "utf-8"
},
"message": "Pushing to https://**redacted**@github.com/ecomplus/storefront.git\nPOST git-receive-pack (1135 bytes)\nerror: failed to push some refs to 'https://**redacted**@github.com/ecomplus/storefront.git'\n",
"stack": "Error: Pushing to https://**redacted**@github.com/ecomplus/storefront.git\nPOST git-receive-pack (1135 bytes)\nerror: failed to push some refs to 'https://**redacted**@github.com/ecomplus/storefront.git'\n\n at GitExecutorChain.onFatalException (/home/ubuntu/renovateapp/node_modules/simple-git/src/lib/runners/git-executor-chain.js:60:87)\n at GitExecutorChain. (/home/ubuntu/renovateapp/node_modules/simple-git/src/lib/runners/git-executor-chain.js:51:28)\n at Generator.throw ()\n at rejected (/home/ubuntu/renovateapp/node_modules/simple-git/src/lib/runners/git-executor-chain.js:6:65)\n at runMicrotasks ()\n at processTicksAndRejections (internal/process/task_queues.js:97:5)"
}
}
DEBUG: Passing repository-changed error up(branch="renovate/docker-digests-pin")
INFO: Repository has changed during renovation - aborting
...
We can skip updates for GH Actions as in this case, is there any other way to skip this update besides the Dependency Dashboard? Otherwise I will remove the husky hook for a while and test again.
This might be related to GitHub app permissions. Can you or whoever is an org admin to go to https://github.com/organizations/ecomplus/settings/installations and then look for something like this:
then you should see something like this:
Eventually it should look like this:
To disable it, I think you can do this:
{
"github-actions": {
"enabled": false
}
}
But it sounds like you'd prefer to keep it enabled but grant the access rights.
@rarkins you're a hero :100:
https://github.com/ecomplus/storefront/pull/308 https://github.com/ecomplus/storefront/pull/307
Haven't seen this auth scope update request, my junior mistake, sorry :stuck_out_tongue:
Which Renovate are you using?
WhiteSource Renovate App
Which platform are you using?
GitHub.com
Have you checked the logs? Don't forget to include them if relevant
We have several jobs done, even today, but no PR has been opened in the past few weeks (used to work before), below the debug of the last job, with status
repository-changed
:What would you like to do?
I want PRs back (used to work, no more working and I don't know why :disappointed: ) to our monorepo https://github.com/ecomplus/storefront with following config: