feat: Integrate Reusable SonarCloud Analysis Workflow with Notifications & Stale Handling#2
Closed
feat: Integrate Reusable SonarCloud Analysis Workflow with Notifications & Stale Handling#2
Conversation
Collaborator
Author
|
@lkkande-BB closing this PR for now |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This pull request introduces a reusable GitHub Actions workflow tailored for SonarCloud analysis. Designed with the open source community in mind, this workflow streamlines continuous code quality checks, incorporates robust notification systems, and automates stale issue/pr management for effective project maintenance.
Detailed Changes:
Workflow Reusability: Configured the workflow for easy adoption across different repositories by externalizing parameters like secrets and project keys.
Notifications Setup: Integrated notifications to alert contributors of failed checks via commonly used platforms such as Slack and Gmail.
Handling Stale Contributions: Implemented a stale management strategy to automate flagging of inactive issues and pull requests, with prompts for action before closing them.
Addresses #1