Version updated for https://github.com/lowlydba/are-we-good to version v1.0.2. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary The “are-we-good” GitHub Action aggregates the statuses of multiple jobs and matrices within a workflow into a single, unified pass/fail status check. It automates the evaluation of complex workflows by allowing configuration of skip, fail, and cancel conditions for specific jobs, ensuring streamlined branch protection and workflow monitoring. Key capabilities include generating a markdown summary of results and providing flexible rules for handling skipped or advisory jobs.

Version updated for https://github.com/lowlydba/are-we-good to version v1.0.1. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary The “are-we-good” GitHub Action consolidates the statuses of multiple jobs or matrix configurations in a workflow into a single pass/fail result, simplifying status checks for branch protection rules. It automates the evaluation of complex CI workflows by allowing specific jobs to fail, be skipped, or cancelled without affecting the overall status, and provides a markdown summary for better visibility. This action is particularly useful for streamlining decision-making in workflows with multiple dependencies or optional tasks.

Version updated for https://github.com/lowlydba/are-we-good to version v1.0.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary The “are-we-good” GitHub Action consolidates the statuses of multiple jobs and matrix builds into a single pass/fail status check, simplifying CI/CD workflows and enabling easier enforcement of branch protection rules. It automates the evaluation of job outcomes, allowing specific jobs to fail, cancel, or skip without affecting the overall status, and provides a clear, optional markdown summary of results. This action helps streamline complex workflows and improves visibility into the overall pipeline health.