Test PR comment and summary features#11
Merged
Merged
Conversation
- Enable comment-on-pr in workflow - Enable add-to-summary in workflow - Add pull-requests write permission - Minor README update to trigger workflow
📦 Version PreviewThis PR will create version: v1.0.7-test.1
|
- Remove 'Will be published as pre-release tag' line - Remove 'Will be published when merged to main' line - Keep only version and type information
📦 Version PreviewThis PR will create version: v1.0.7-test.2 Type: Pre-release |
- Update existing bot comment instead of creating new ones - Change wording from 'will create' to 'has been tagged as' - Check for existing comment by searching for '📦 Version' marker
- Use heredoc to create comment body file - Use placeholders and sed to substitute values - Avoids YAML parsing issues with multiline strings
Remove placeholder approach and sed substitution in favor of direct variable expansion in heredoc. This simplifies the code and avoids YAML parsing issues. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Change from 'Type: **X**' to inline format '**VERSION** (TYPE)' to avoid YAML parser confusion with colons. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Use printf instead of heredoc for creating comment body to completely avoid YAML parser confusion with heredoc markers. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Change author.login from 'github-actions' to 'github-actions[bot]' to properly match GitHub Actions bot comments. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
📦 VersionThe latest version for this PR has been tagged as v1.0.7-test.3 (Pre-release) |
📦 Version: v1.0.7-test.4 (Pre-release) |
📦 Version: v1.0.7-test.5Pre-release |
Add branch name, bump type, and previous version to PR comment for better visibility. Also add these as action outputs.
📦 Version: v1.0.7-test.6Type: Pre-release |
📦 Version: v1.0.7-test.7
|
📦 Version: v1.0.7-test.8
|
📦 Version: v1.0.7-test.9
|
Extract job summary logic into separate step for better organization and consistency with PR comment step. Use same table format for both.
📦 Version: v1.0.7-test.10
|
📦 Version: v1.0.7-test.10
|
- Document new outputs (branch, previous-version, bump-type) - Add section showing PR comment and job summary features - Clarify comment-on-pr requires enable-prerelease - Show table format example
📦 Version: v1.0.7-test.10
|
Prevents 'tag already exists' error when workflow runs multiple times on same commit.
📦 Version: v1.0.7-test.10
|
📦 Version: v1.0.7-test.10
|
github-actions Bot
pushed a commit
that referenced
this pull request
Feb 13, 2026
* Test PR comment and summary features - Enable comment-on-pr in workflow - Enable add-to-summary in workflow - Add pull-requests write permission - Minor README update to trigger workflow * Simplify PR comment - remove unnecessary note - Remove 'Will be published as pre-release tag' line - Remove 'Will be published when merged to main' line - Keep only version and type information * Reuse PR comment and fix wording - Update existing bot comment instead of creating new ones - Change wording from 'will create' to 'has been tagged as' - Check for existing comment by searching for '📦 Version' marker * Fix YAML syntax by using heredoc with placeholders - Use heredoc to create comment body file - Use placeholders and sed to substitute values - Avoids YAML parsing issues with multiline strings * fix: simplify PR comment generation using direct variable expansion Remove placeholder approach and sed substitution in favor of direct variable expansion in heredoc. This simplifies the code and avoids YAML parsing issues. * fix: simplify comment format to avoid YAML parsing issues Change from 'Type: **X**' to inline format '**VERSION** (TYPE)' to avoid YAML parser confusion with colons. * fix: replace heredoc with printf to avoid YAML parsing Use printf instead of heredoc for creating comment body to completely avoid YAML parser confusion with heredoc markers. * fix: correct GitHub Actions bot username Change author.login from 'github-actions' to 'github-actions[bot]' to properly match GitHub Actions bot comments. * Update PR comment to cleaner one-line format * Move type to separate line in PR comment * Add comprehensive info to PR comment Add branch name, bump type, and previous version to PR comment for better visibility. Also add these as action outputs. * Format PR comment as table * Only show PR comment when pre-release is enabled * Only show job summary when on main or pre-release enabled * Separate job summary into its own step Extract job summary logic into separate step for better organization and consistency with PR comment step. Use same table format for both. * Remove Previous field from PR comment and summary * Update README with PR comment and job summary documentation - Document new outputs (branch, previous-version, bump-type) - Add section showing PR comment and job summary features - Clarify comment-on-pr requires enable-prerelease - Show table format example * Add check to skip if tag already exists Prevents 'tag already exists' error when workflow runs multiple times on same commit. * Remove redundant comments ---------
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Testing the new features:
comment-on-pr: true- Should add a comment to this PR with version previewadd-to-summary: true- Should add version info to the job summaryExpected version:
v1.0.7-test.1(pre-release from test/* branch)This PR is just for testing the new features added in PR #9.