Skip to content

Notify CI failures on Slack#195

Merged
mergify[bot] merged 1 commit intomasterfrom
waiting-for-dev/slack
Nov 22, 2022
Merged

Notify CI failures on Slack#195
mergify[bot] merged 1 commit intomasterfrom
waiting-for-dev/slack

Conversation

@waiting-for-dev
Copy link
Copy Markdown
Contributor

Summary

We use the circleci/slack orb to notify whenever a CircleCI job fails. All jobs are included.

Currently, the CircleCI context has been configured to point to the #ci-notifications channel on Solidus' Slack workspace, where we have created the required Slack app.

Screenshot 2022-11-18 at 05 25 51

Checklist

Check out our PR guidelines for more details.

The following are mandatory for all PRs:

  • I have written a thorough PR description.
  • I have kept my commits small and atomic.
  • I have used clear, explanatory commit messages.

The following are not always needed (cross them out if they are not):

  • [ ] I have added automated tests to cover my changes.
  • I have attached screenshots to demo visual changes.
  • [ ] I have opened a PR to update the guides.
  • [ ] I have updated the README to account for my changes.

We use the circleci/slack orb [1] to notify whenever a CircleCI job
fails. All jobs are included.

Currently, the CircleCI context has been configured to point to the
'#ci-notifications' [2] channel on Solidus' Slack workspace [3], where we have
created the required Slack app [4].

[1] - https://circleci.com/developer/orbs/orb/circleci/slack
[2] - https://solidusio.slack.com/archives/C04C337T6P2
[3] - https://solidusio.slack.com
[4] - https://circleci.com/docs/slack-orb-tutorial/
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Nov 21, 2022

It looks like this PR is missing a label to determine the type of change it introduces. The maintainer should add one of the following labels:

  • bug for bugfixes.
  • enhancement for new features and improvements.
  • documentation for documentation changes.
  • security for security patches.
  • removed for feature removals.
  • infrastructure for internal changes that should not go in the changelog.

Additionally, the maintainer may also want to add one of the following:

  • breaking for breaking changes.
  • deprecated for feature deprecations.

Once the correct labels have been set, simply remove the needs changelog label label from this PR so I can merge it.

@mergify mergify Bot added the needs changelog label Needs a label to determine the type of change. label Nov 21, 2022
@waiting-for-dev waiting-for-dev added enhancement Improves an existing feature. infrastructure Internal change — changelog entry not needed. and removed enhancement Improves an existing feature. needs changelog label Needs a label to determine the type of change. labels Nov 21, 2022
Copy link
Copy Markdown
Member

@elia elia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📬

@kennyadsl kennyadsl requested a review from a team November 22, 2022 14:36
@mergify mergify Bot merged commit 6b85cc1 into master Nov 22, 2022
@mergify mergify Bot deleted the waiting-for-dev/slack branch November 22, 2022 14:37
forkata pushed a commit to SuperGoodSoft/solidus_dev_support that referenced this pull request Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Internal change — changelog entry not needed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants