Skip to content

ci(dependabot): slack alert #34

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

MuHamza30
Copy link

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.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause a breaking change)
  • Tests (adds or updates tests)## What
    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.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause a breaking change)
  • Tests (adds or updates 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

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

  • 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

@MuHamza30 MuHamza30 requested a review from sufyankhanrao May 29, 2025 03:57
@MuHamza30 MuHamza30 self-assigned this May 29, 2025
Copy link

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.

1 participant