This repository has been archived by the owner on Mar 24, 2024. It is now read-only.
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.
User-Facing Changes
None
Description
PRs submitted from a fork repo don't have a valid
github.event.pull_request.head.ref
. For example #1524 failed with:Determining the checkout info /usr/bin/git branch --list --remote origin/feature/add_web_build_command /usr/bin/git tag --list feature/add_web_build_command Error: A branch or tag with the name 'feature/add_web_build_command' could not be found
It's possible this could be fixed by checking out
head.sha
instead ofhead.ref
. However, we originally switched to the head commit because Chromatic claimed to need it, but I'm fairly confident that is not the case.There are also advantages to testing the PR merge commit (PR merged with latest main) - it means the likelihood of a CI failure post-merge is reduced.
Therefore, switching back to using Github's default behavior. There is still some outstanding work to make PRs work completely from fork repos (Chromatic token isn't accessible - see #1608), but this at least gets us one step closer.
Closes #1626
Closes #1627