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
We're in the middle of a migration between the Mend-hosted (SAAS) renovate[bot] and a self-hosted Renovate bot, running under Mend Renovate Community Edition, all on github.com.
As part of this, we've got the following configuration set in our config.js:
// Via https://docs.renovatebot.com/configuration-options/#gitignoredauthorsgitIgnoredAuthors: ["29139614+renovate[bot]@users.noreply.github.com"],// Via https://docs.renovatebot.com/configuration-options/#ignoreprauthorignorePrAuthor: true,
We have a number of Dependency Dashboard issues that were created by renovate[bot] and are continued to be updated by our self-hosted bot.
When ticking a checkbox on an issue, such as:
Check this box to trigger a request for Renovate to run again on this repository
We receive no feedback from Renovate, nor does it execute the run as expected.
Digging into the logs, we see that Mend Renovate Community Edition is ignoring the event as a non-bot GitHub issue:
Pull Requests are unaffected, and continue to be updated as-is.
Would it make sense for the Mend Renovate Community Edition code to make this configurable - somehow 🫣 - to make it so a migration is possible?
This is using Mend Renovate Community Edition 7.5.0
(I believe this is more likely to be an issue with Mend Renovate Community Edition, than it is Renovate OSS, due to it being webhook related, hence raising here)
We're in the middle of a migration between the Mend-hosted (SAAS)
renovate[bot]
and a self-hosted Renovate bot, running under Mend Renovate Community Edition, all ongithub.com
.As part of this, we've got the following configuration set in our
config.js
:We have a number of Dependency Dashboard issues that were created by
renovate[bot]
and are continued to be updated by our self-hosted bot.When ticking a checkbox on an issue, such as:
We receive no feedback from Renovate, nor does it execute the run as expected.
Digging into the logs, we see that Mend Renovate Community Edition is ignoring the event as a
non-bot GitHub issue
:Pull Requests are unaffected, and continue to be updated as-is.
Would it make sense for the Mend Renovate Community Edition code to make this configurable - somehow 🫣 - to make it so a migration is possible?
This is using Mend Renovate Community Edition 7.5.0
(I believe this is more likely to be an issue with Mend Renovate Community Edition, than it is Renovate OSS, due to it being webhook related, hence raising here)
(possibly related to #557)
The text was updated successfully, but these errors were encountered: