Skip to content

Tags: labrynx/auto_comments

Tags

v1.2.0

Toggle v1.2.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #25 from labrynx/development

Development

v1.1.3

Toggle v1.1.3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Update auto_comments.yml

chore: update workflow configuration for enhanced robustness and functionality

- Updated environment variables format from single to double quotes.
- Improved dependency installation: now only installs jq and curl if they’re missing.
- Enhanced input data validation with more detailed error messages.
- Upgraded actions/checkout to v4 and added Node.js setup using actions/setup-node@v3.
- Added project type detection for Node.js (and Yarn-based Node), Maven, Gradle, and Python with corresponding build, test, and lint commands.
- Introduced dependency caching using actions/cache@v4 based on project type.
- Implemented a retry_command function (via retry.sh) to reattempt build and test commands on transient failures.
- Improved build, test, and coverage handling, including actual coverage parsing for Node projects.
- Added steps to gather commit and PR details (labels, changed files).
- Enhanced the PR comment to include detailed summaries of linting, test results, and coverage.
- Added debug logging that runs when DEBUG is set to true.

v1.1.2

Toggle v1.1.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #17 from alessbarb/dependabot/github_actions/actio…

…ns/checkout-4

Bump actions/checkout from 3 to 4

v1.1.1

Toggle v1.1.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #15 from alessbarb/v1.1.1

1. Removed the introductory note about potentially using pull_request_target for forked pull requests.

2. Added project detection for Yarn by checking for yarn.lock, setting PROJECT_TYPE=node-yarn, and using yarn install, yarn test, and yarn lint.

3. Introduced dependency caching through two new steps: one that prepares a cache key and another that uses actions/cache@v3. Each recognized project type now defines a CACHE_PATH and a DEPENDENCY_FILE (for example, package-lock.json or pom.xml) to enable caching.

4. Added a retry function for build and test commands. A new shell script named retry.sh is generated, containing a retry_command() function that attempts a command multiple times with a brief pause between tries.

5. Expanded coverage logic to check for actual coverage files, such as coverage/coverage-summary.json when Node-based projects are detected, extracting a coverage percentage using jq. For other project types, placeholder coverage strings are provided.

6. Implemented stricter lint failure handling: the lint step now runs under set -e, causing the pipeline to fail immediately if linting fails. Previously, lint errors were ignored.

7. Replaced extra placeholders with more dynamic or real coverage and lint outputs. The build/test steps now exit early if PROJECT_TYPE is unknown, and the newly added retry logic wraps the build/test commands.

8. Used sed with the expression s/^ {10}// to strip indentation from the code block that writes retry.sh, preventing syntax errors caused by extra leading spaces.

9. Improved Markdown formatting by inserting a blank line after the <summary>Files Changed</summary> tag so that links within the collapsible section render correctly in GitHub.

v1.0.0

Toggle v1.0.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #13 from alessbarb/patch-202502-1

We switched from `actions/checkout@v2` to `@v3` for better security and performance, and added a new `PR_URL` variable so we can store the actual PR link instead of overloading `PR_TITLE` (which now strictly refers to the PR’s title). The README also goes into more detail about how the action validates inputs and retries API calls—basically explaining the logic for ensuring we don’t fail on transient errors. We clarified the debug logging process (toggling `DEBUG` to `true` provides additional logs) and added a note about GitHub’s 65,536-character limit on comment bodies, which we handle by truncating any overly long messages. Overall, it’s a more complete overview of how the action runs and what each step does.