Repository navigation
test(e2e-command): cover fork commands in the platform harness - #55
Merged
Merged
Conversation
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
allow-forks, dispatch from the target branch for forks, the contract check on the workflow that will run, SHA-pinned checkout, andcache-mode: readwith a cache probe.repro/fork-command/run.sh: two fork PRs with the same request both succeed, and a fork PR into a branch without the contract is refused.This tests the loft-enterprise change before it is opened there.
Test plan
sticky-pr-comment/v1tagshellcheck -x repro/fork-command/run.sh, parses under bash 3.2repro/fork-command/run.shRelated to DEVOPS-1541