chore: share guarded CoinPay PR commands across repositories - #8
Merged
Merged
Conversation
ThreatCrush Security Scan0 finding(s) No findings. |
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 reusable
pr-commands.ymlworkflow so repositories can install manual CoinPay PR commands with a small pinned caller. The shared job verifies the comment author's current write/maintain/admin permission, checks named credentials, runs an immutable action revision, and times out after five minutes. It never checks out PR code.The caller example and setup docs distinguish explicit contributor-wallet payment requests from business-issued formal invoices. Formal invoice publishing remains disabled in the documented configuration; this change defines no automatic PR rate or payout.
Validation: typecheck, 215 existing action tests, 20 workflow authorization/setup tests, YAML parsing, and bundle rebuild with no
distchanges. The exact pinned action bundle also passed mocked dry-run, explicit-wallet creation, and disabled formal-invoice cases with real sockets disabled; no live comments or financial resources were created.