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 Apr 4, 2024. It is now read-only.
We have previously used github-slack integration to keep developers informed about their workflow progress in our organization.
They simply subscribe to the workflow using
/github subscribe owner/repo workflows:{name:"your workflow name" event:"workflow event" actor:"actor name"}
Since bors is merging all the PR's the notifications are not being sent.
Is there anyway, the workflows are triggered by original author instead of bors which I think not possible. But is there anything else we can do here.
The text was updated successfully, but these errors were encountered:
I have no idea, but in general, I recommend using GitHub Merge Queues instead of Bors if it's possible, since it's a first-party feature and generally integrates with everything else better.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have previously used github-slack integration to keep developers informed about their workflow progress in our organization.
They simply subscribe to the workflow using
/github subscribe owner/repo workflows:{name:"your workflow name" event:"workflow event" actor:"actor name"}
Since bors is merging all the PR's the notifications are not being sent.
Is there anyway, the workflows are triggered by original author instead of bors which I think not possible. But is there anything else we can do here.
The text was updated successfully, but these errors were encountered: