[ci] Post verification summary as sticky PR comment - #64
Open
devin-ai-integration[bot] wants to merge 1 commit into
Open
[ci] Post verification summary as sticky PR comment#64devin-ai-integration[bot] wants to merge 1 commit into
devin-ai-integration[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: Andrew He <he.andrew.mail@gmail.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
⚠ Verification result
Results
Past results
|
GCC Code Coverage Report📂 Overall coverage
|
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
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.
Summary
The verification summary tables (pass/fail/skip counts, per-file timings) only appeared in the docs job's step summary, because
competitive-verifier docs --write-summarywrites them to$GITHUB_STEP_SUMMARY— the CLI has no other output target, and thechecksubcommand doesn't support--write-summaryat all.This snapshots that step summary right after the
Docsstep (cp "$GITHUB_STEP_SUMMARY" $RUNNER_TEMP/verify-summary.md— each step gets its own summary file, so this captures only the verification tables) and posts it as a sticky PR comment (header: verify) via the samemarocchino/sticky-pull-request-commentaction already used for coverage.Link to Devin session: https://app.devin.ai/sessions/92894aa8dba0415e94e3df205442e7ee
Requested by: @ecnerwala