feat: /codeboarding posts a new comment per run instead of updating in place#14
Merged
Merged
Conversation
…n place On-demand /codeboarding (issue_comment) now uses a run-unique sticky header, so each invocation creates a fresh comment and leaves earlier ones (the auto on-open comment and prior /codeboarding results) intact. Automatic pull_request runs keep the stable header and update in place as before. The header is resolved once in the guard step (written up front so the failure-comment step always has it).
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.
Each
/codeboardinginvocation now posts a fresh comment via a run-unique sticky header, leaving the auto on-open comment and any prior/codeboardingresults untouched.Automatic
pull_requestruns keep the stable header and update their comment in place as before.