Version updated for https://github.com/sankichi92/list-changed-directories to version v1.2.0. This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary The list-changed-directories GitHub Action identifies and outputs a list of directories that have been modified and contain a specified target file, based on changes detected in push or pull_request events. It solves the problem of efficiently targeting only changed directories in workflows, particularly in monorepos or codebases with multiple directories, without the need to create multiple workflows or run jobs unnecessarily.

Version updated for https://github.com/vig-os/sync-issues-action to version v0.1.1. This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary The “Sync Issues and PRs Action” is a GitHub Action designed to automate the synchronization of repository issues and pull requests into organized markdown files. It captures all relevant details, including comments, conversations, metadata, and review threads, enabling users to archive or process repository information outside of GitHub.

Version updated for https://github.com/vmvarela/sonarqube-ce-sarif-action to version v0.3.1. This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action integrates SonarQube Community Edition (CE) with GitHub, enabling features like pull request (PR) decoration, inline code annotations, issue summaries, and GitHub Security Tab integration that are typically unavailable in the CE version. It automates the process of converting SonarQube scan results into SARIF format, providing actionable insights and better visibility of code quality and security issues directly within the GitHub interface.

Version updated for https://github.com/ynathaniel-source/whydiditfail-action to version v1.2.0. This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary The “Why Did It Fail?” GitHub Action automates the analysis of failed GitHub workflows by using AI to extract and explain the root cause of errors from failure logs. It provides concise explanations, confidence scores, and actionable fix suggestions directly in the GitHub Actions UI, saving developers time and effort in debugging.

Version updated for https://github.com/zktx-io/sui-mvr-provenance to version v0.3.9. This action is used across all versions by 3 repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action automates the process of building and deploying Move packages using the Sui CLI, while generating verifiable provenance metadata and registering it in the Move Registry (MVR). It simplifies the creation of trustable and auditable smart contracts by producing SLSA-compliant provenance bundles and metadata for on-chain verification.

Version updated for https://github.com/aboutexo04/commit-formatter to version v1.0.0. This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary The Commit Message Formatter GitHub Action automates the formatting of commit messages to adhere to the Conventional Commits specification using AI models via OpenRouter. It solves the problem of inconsistent or informal commit messages by standardizing them across projects, supports multiple languages, and can intelligently skip commits already in the correct format.

Version updated for https://github.com/cv/pi-action to version v1.4.4. This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary The pi-action GitHub Action automates interactions with the pi coding agent to assist with issue handling, pull request reviews, and other repository tasks, triggered by customizable commands (e.g., @pi) in comments or upon issue/PR creation. It enhances collaboration by enabling automated code reviews, enforcing commit conventions, and integrating with large language models (LLMs) for intelligent responses, while providing robust security controls and bot allowlists.

Version updated for https://github.com/Flow-Scanner/lightning-flow-scanner to version action-v3.3.1. This action is used across all versions by 0 repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary The Lightning Flow Scanner GitHub Action is a tool designed to analyze and optimize Salesforce Flows by detecting potential issues such as unsafe contexts, queries in loops, hardcoded IDs, and other anti-patterns. It helps developers automate the identification of errors and inefficiencies that could lead to runtime failures, security risks, or deployment issues, improving the quality and maintainability of Salesforce Flow implementations.

Version updated for https://github.com/groda/github-traffic-archiver to version v2. This action is used across all versions by 1 repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action automates the collection and archival of repository traffic statistics (clones and views), addressing GitHub’s 14-day data retention limit by storing metrics in a dedicated repository for long-term historical analysis. It streamlines the process by fetching daily traffic data, updating logs, and maintaining a centralized “Metrics Vault” for tracking multiple repositories.