Version updated for https://github.com/CatChen/accept-to-ship-action to version v0.8.6. This action is used across all versions by 0 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 accept-to-ship-action is a GitHub Action that automates the process of merging pull requests once they receive approval. By adding a specific hashtag (e.g., #accept2ship) to a pull request, this action automatically handles the merging process, eliminating the need for manual intervention from the requester or approver. It supports features like auto-merge integration, customizable hashtags, and the ability to wait for checks to pass before merging, streamlining the pull request workflow.

Version updated for https://github.com/CatChen/eslint-suggestion-action to version v4.1.30. This action is used across all versions by 119 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 eslint-suggestion-action GitHub Action automates the process of running ESLint on code changes in a Pull Request and provides inline feedback for issues detected in the modified lines. If ESLint can auto-fix a problem, it suggests the fix directly within the Pull Request, allowing developers to review and accept the changes. This action eliminates noise by focusing exclusively on new changes, helping maintain code quality without addressing pre-existing issues.

Version updated for https://github.com/CatChen/oxlint-suggestion-action to version v1.0.5. This action is used across all versions by 0 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 oxlint-suggestion-action GitHub Action integrates Oxlint into your CI/CD pipeline to automate code linting and review processes for Pull Requests. It provides targeted inline feedback by posting review comments only on the lines modified in the Pull Request, reducing noise from pre-existing issues outside the diff. This action streamlines code quality enforcement and enhances collaboration during code reviews.

Version updated for https://github.com/CatChen/token-who-am-i-action to version v2.0.20. This action is used across all versions by 3 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 token-who-am-i-action GitHub Action identifies and retrieves detailed metadata about the identity associated with a provided GitHub token. It automates the process of extracting key attributes such as username, ID, email, token type, and permission scopes, helping developers understand the context and capabilities of the token they are using. This action is particularly useful for debugging and managing access control in workflows.

Version updated for https://github.com/CatChen/oxlint-suggestion-action to version v1.0.4. This action is used across all versions by 0 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 oxlint-suggestion-action GitHub Action runs Oxlint to analyze code changes in a Pull Request and provides inline feedback by adding review comments directly to modified lines, ensuring that pre-existing issues outside the diff do not create unnecessary noise. It automates the process of identifying and addressing linting issues specific to the changes introduced in a PR, helping maintain code quality and streamlining code review. Key features include the ability to flag changes, request modifications, and optionally fail the workflow based on linting results.

Version updated for https://github.com/CatChen/token-who-am-i-action to version v2.0.19. This action is used across all versions by 3 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 token-who-am-i-action is a GitHub Action that retrieves identity information associated with a provided GitHub token, including details like username, email, user type (e.g., User or Bot), token permissions, and more. It automates the process of identifying the entity behind a token, making it easier for developers to understand the context and capabilities of the token in workflows. This action is particularly useful for debugging and managing tokens in composite GitHub Actions.

Version updated for https://github.com/CatChen/eslint-suggestion-action to version v4.1.28. This action is used across all versions by 117 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action, eslint-suggestion-action, runs ESLint on code changes in a pull request and provides targeted, inline feedback only for the modified lines. It automates the process of identifying and suggesting fixes for linting issues, including offering auto-fix suggestions that can be applied directly. By focusing solely on new changes, it reduces noise for pre-existing code that may not meet ESLint standards.

Version updated for https://github.com/CatChen/oxlint-suggestion-action to version v1.0.3. This action is used across all versions by 0 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 oxlint-suggestion-action GitHub Action runs Oxlint to analyze code changes in a Pull Request and provides inline feedback by posting review comments for any diagnostics found on modified lines. It streamlines the code review process by focusing only on changes introduced in the Pull Request, avoiding unnecessary noise from pre-existing issues. This action helps automate code quality checks and ensures targeted, actionable feedback during development.

Version updated for https://github.com/CatChen/token-who-am-i-action to version v2.0.18. This action is used across all versions by 3 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 token-who-am-i-action is a GitHub Action that identifies and retrieves detailed metadata about the user or bot associated with a given GitHub token. It automates the process of determining the token’s identity, type, permissions, and other attributes such as username, email, and access scopes. This action is particularly useful for developers who need contextual information about authentication tokens when building or debugging GitHub Actions workflows.