ci(dependabot): slack alert #34
Open
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.
What
Write a summary of the changes made in the PR.
Why
Exlpain the reasons for the changes.
Type of change
Select multiple if applicable.
Added functionality in the GitHub Actions workflow to send a Slack alert when all checks for a pull request complete successfully.
Why
To improve team visibility and communication by notifying the team on Slack once a PR passes all checks, reducing the time to merge and ensuring everyone stays in the loop.
Type of change
Select multiple if applicable.
Dependency Change
If a new dependency is being added, please ensure that it adheres to the following guideline https://github.com/apimatic/apimatic-codegen/wiki/Policy-of-adding-new-dependencies-in-the-core-libraries
Breaking change
If the PR is introducing a breaking change, please ensure that it adheres to the following guideline https://github.com/apimatic/apimatic-codegen/wiki/Guidelines-for-maintaining-core-libraries
Testing
Triggered the workflow on a test PR to ensure:
Slack alert is sent only after all checks succeed.
Alert includes correct PR metadata (title, URL, status).
Verified with a test Slack channel.
Checklist
My code follows the coding conventions
I have performed a self-review of my own code
I have commented my code, particularly in hard-to-understand areas
I have added new unit tests
Documentation (adds or updates documentation)
Refactor (style improvements, performance improvements, code refactoring)
Revert (reverts a commit)
CI/Build (adds or updates a script, change in external dependencies)
Dependency Change
If a new dependency is being added, please ensure that it adheres to the following guideline https://github.com/apimatic/apimatic-codegen/wiki/Policy-of-adding-new-dependencies-in-the-core-libraries
Breaking change
If the PR is introducing a breaking change, please ensure that it adheres to the following guideline https://github.com/apimatic/apimatic-codegen/wiki/Guidelines-for-maintaining-core-libraries
Testing
List the steps that were taken to test the changes
Checklist