Version updated for https://github.com/kitsuyui/gh-build-size to version v0.1.2. This action is used across all versions by 6 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary gh-build-size is a GitHub Action that automates the measurement and reporting of built artifact sizes for pull requests and the default branch. It compares build outputs (e.g., JavaScript, CSS, or WebAssembly files) against a baseline, generates size metrics (raw, gzip, brotli), enforces size limits, and posts PR comments with detailed insights. Additionally, it can publish JSON reports and visual badges for tracking size changes, helping developers monitor and optimize build sizes effectively.

Version updated for https://github.com/kitsuyui/gh-counter to version v1.5. This action is used across all versions by 6 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary gh-counter is a GitHub Action designed to track and count specific code markers (e.g., TODO, FIXME, @ts-ignore) in pull requests and the default branch of a repository. It automates tasks such as evaluating PR changes against configurable thresholds, generating repository-wide dashboards, and optionally publishing JSON reports and badge assets for tracking these markers over time. This tool simplifies codebase quality monitoring and enables teams to enforce consistent coding practices with minimal setup.

Version updated for https://github.com/kitsuyui/gh-counter to version v1.4. This action is used across all versions by 6 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary gh-counter is a GitHub Action designed to automate the tracking and comparison of configurable code markers, such as TODO or FIXME, in pull requests and the default branch of a repository. It simplifies setup while providing functionality to generate managed pull request comments and publish JSON or badge assets for tracking code signals. This helps maintain visibility into technical debt and code annotations, making it easier to monitor and manage such markers across a codebase.