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
{{ message }}
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.
I'm not sure if there's any way around this, but it would be really nice if we could somehow overwrite the review requirement for PRs opened by web3-bot. @galargh, any ideas?
The text was updated successfully, but these errors were encountered:
I don't think there's a quick way around this; we could make the bot an administrator so it can skip the checks, but that seems like a can of worms.
As an alternative, the bot has write permissions, so I wonder if we could have a second bot approve the changes. Adds more steps and setup, but seems safer than giving a bot admin permissions or dropping the safety requirements entirely.
Another option, and what I would say is best, is to obey the repo's protections. If I've set up the repo to require approvals from maintainers, I would be surprised if our bots were engineered to ignore those. Even for CI changes which are presumably safe.
I'm not sure if there's any way around this, but it would be really nice if we could somehow overwrite the review requirement for PRs opened by
web3-bot
. @galargh, any ideas?The text was updated successfully, but these errors were encountered: