Configure action to respond to issue checkboxes

[jessehouwing]

When Renovate registers a pull-request, it has a bunch of checkboxes in it.

I'm trying to make renovate respond immediately to said pull request, but it looks like this isn't built into the action.

Reason I need this, is cause I'm trying to enable renovate on a repo within an org I don't own, so I can't give the app permissions to do its thing. Plus, I need to run on Windows.

I tried adding

  issue_comment:
    types: [edited]
  issues:
    types: [edited]

But this feels like MASSIVE overkill. Every run takes 5 minutes+.

Is there a way to pass in a specific pull request to npx renovate or this github-action to make renovate only re-evaluate that issue or pull request?

[viceice]

no. even the github app will do a full rerun on the repo on checkbox check

[jessehouwing]

wow! That's quite a lot of CPU burning there :).

[viceice]

btw: you should cache <cacheDir>/cache/renovate/repository/**/*.json between runs. it shold speedup your runs

[jessehouwing]

This project only works on windows and requires NPM to be run on a windows host.

https://github.com/microsoft/azure-devops-extension-tasks

It's the native 7z node package of one of the build tasks in the lock file that trips up renovate.

[rarkins]

It now runs against a single repo. I'd love to use the app, but Microsoft won't install it in the Microsoft org.

FYI the Renovate app (github.com/apps/renovate) is installed into github.com/microsoft, if that's what you mean? It's been installed into both public and private repos, including https://github.com/microsoft/lage/blob/master/renovate.json5 for example.

[jessehouwing]

Hmmm not in mine... So it's probably selectively turned on. Still wont let me run on windows though.

[rarkins]

Yeah, it's "Selected repositories" mode, and you're right regarding windows

[jessehouwing]

you could use a self hosted runner too speedup things or add caching to setup node action.

you should only use windows hosted runner for projects that really require it. most projects can be handled with Linux even all developers are only using windows.

can you elaborate more why you need a windows renovate runner.

Caching setup-node seems to add a bit of speed, but it does require a few hacks due to the fact that npx renovate doesn't leave a package-lock.json. So there is no cache key.

I'm looking at running npm show renovate version >> renovate-lock.json and then using that as a cache key.

I'm looking at using npm install renovate -g --prefix $PATH_I_DEFINE to then be able to cache it.