Try to enable Test commands to run from forked branches. #3740
Conversation
This file contains 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
davinchia
changed the title
|
/test connector=source-file
|
|
/test connector=source-file
|
davinchia
changed the title
|
/test connector=source-file
|
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.
What
Today the test/publish commands always pull from the airbyte repo regardless of where the PR branch lives in. This means we cannot run the test/publish command on forked PRs.
Configure the checkout action to pull from the PR branch's repository instead of always defaulting to the repository the PR lives in.
Ran one integration test to show this change is no-op if the PR branch is from the Airbyte repo. The real test is running this command on #3660 .
Pre-merge Checklist
Recommended reading order