-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(IDX): update slack notification #181
Conversation
done | ||
echo "channels=${CHANNELS}" >> $GITHUB_OUTPUT | ||
TEAM=${{ steps.get-reviewers.outputs.result }} | ||
CHANNEL=$(jq -r ".$TEAM" .github/workflows/team-channels.json) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should handle the case where the team doesn't have a channel assigned yet. The following step would fail in that case I assume.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we want it to fail? So we know the team can't be notified?
GitHub Sync PR#181 / chore(IDX): update slack notification [GitHub PR 181](#181) (branch: update-slack-notification) See merge request dfinity-lab/public/ic!19649
It seems that the action "ready for review" triggers before "review requested" so the payload doesn't always have the complete teams. This fix changes the trigger and will both trigger if a PR is directly opened as a non-draft and if additional reviewers are added later.