gradle.yml: make it run on forks #37788
Merged
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @alafanechere and the rest of your teammates on |
octavia-squidington-iii
added
area/connectors
alafanechere
force-pushed
the
augustin/05-03-gradle.yml_make_it_run_on_forks
branch
from
56ba777
to
27b3fd1
Compare
aasimsani
pushed a commit
to taxwire/airbyte
that referenced
this pull request
May 6, 2024
clnoll
pushed a commit
that referenced
this pull request
May 10, 2024
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.
The
gradle.ymlworkflow has a requiredGradle Checkjob. If we want to accept contributions from forks on Java connectors we should make it run on forks.It should be possible as this workflow does not require secret access.
On forks the workflow will not benefit from our S3 gradle cache nor docker login, it might have a performance impact but its tolerable given the small amount of java connectors contribution.