Skip to content

chore: revised Slack notification workflow - #78

Open
burigolucas wants to merge 1 commit into
redhat-cop:mainfrom
burigolucas:ci/revise-slack-workflow
Open

chore: revised Slack notification workflow#78
burigolucas wants to merge 1 commit into
redhat-cop:mainfrom
burigolucas:ci/revise-slack-workflow

Conversation

@burigolucas

Copy link
Copy Markdown
Contributor

The following two fixes are implemented:

  • fixed slack notification formatting: line brakes were not correctly escaped resulting in wrong rendering of the message in the Slack notification
  • added continue on error when slack notification fails: a failed notification will not be shown as a failed workflow, but rather be logged with action required for maintainers

Description

Type of Change

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation changes
  • style: Formatting, missing semi colons, etc; no code change
  • refactor: Refactoring production code
  • test: Adding missing tests, refactoring tests; no production code change
  • chore: Updating configs, etc; no production code change

Pull Request Title

Note: Please ensure your PR title follows Conventional Commits.
Example: feat: add role

  • I have formatted my PR title correctly.

- fixed slack notification formatting
- added continue on error when slack notification fails
@burigolucas
burigolucas requested a review from sabre1041 as a code owner August 31, 2026 11:51
@burigolucas
burigolucas deployed to external-ci August 31, 2026 11:51 — with GitHub Actions Active
@burigolucas burigolucas changed the title chore: revised slack notification workflow chore: revised Slack notification workflow Aug 31, 2026

@tech2734 tech2734 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. The $'...' quoting fix for newlines is correct, and the continue-on-error with actionable warning output is a clean approach — keeps Slack failures from masquerading as code quality issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants