fix(ci): make Slack notifications non-fatal in test_bundles workflow … #9443
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…template
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:
#8864.
Description
This pull request:
test_bundlesGitHub Actions workflow template to ensure that Slack notification steps do not cause CI failures when Slack configuration is missing or misconfigured.The change applies only to the workflow template, so it affects newly generated workflows without modifying existing ones.
In forks and local testing environments, Slack secrets are often unavailable.
Currently, failures in the Slack notification step can cause otherwise successful CI jobs to fail.
Related Issues
This pull request has the following related issues:
randomrepository #8864Questions
No.
Other
No.
Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
{{TODO: add disclosure if applicable}}
@stdlib-js/reviewers