test: e2e self-test (live API + sticky PR comment) - #1
Merged
Conversation
On pull_request / workflow_dispatch: generate a dummy diff PNG and run the action against the live PixelVault API, asserting one upload. Exercises glob → batch → signed URL → sticky PR comment end to end. Needs the PIXELVAULT_API_KEY repo secret. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
📸 PixelVault screenshots
1 uploaded · collection |
Avoids a live upload + quota use on every PR (and fork-PR failures). The full chain — including the sticky PR comment — was verified once in PR #1; keep this as a manual "re-verify against prod" smoke test. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Adds a self-test workflow that runs the action against the live PixelVault API on each PR — glob → batch upload → signed URLs → sticky PR comment. This PR is also the first real end-to-end run of the action; the sticky comment should appear below once the workflow finishes.