Disable CI startup on fork branches

[linghengqian]

• For Update the .sdkmanrc of the master branch #731 and native-maven-plugin lacks runtimeArgs configuration item similar to native-gradle-plugin #685 .
• Disable CI startup on fork branches.
• This is the source of the most annoying email reminders I encountered at Update the .sdkmanrc of the master branch #731. We have discussed something similar at Restrict Github Actions Jobs from being executed on Forked branches oracle/graalvm-reachability-metadata#229.
• 

[dnestoro]

Are you sure that this is the correct syntax? We are using slightly different syntax in the Reachability metadata repository: https://github.com/oracle/graalvm-reachability-metadata/blob/master/.github/workflows/check-new-library-versions.yml#L21

[linghengqian]

• This syntax actually comes from https://github.com/graalvm/native-build-tools/blob/master/.github/workflows/deploy-snapshots.yml#L18 and I just want to be consistent across multiple files. Is there any issue I missed?
• 

[dnestoro]

This looks good to me. My only question is what should I do if I want to run workflow on my fork to verify some changes?

@melix @vjovanov @sdeleuze what do you think about this? Can this have any negative effects (for example on Spring or Micronaut).

[linghengqian]

This looks good to me. My only question is what should I do if I want to run workflow on my fork to verify some changes?

• @dnestoro Both the current project and other projects I collaborate on use the Github Actions workflow_dispatch syntax in the CI configuration file, which means that a Job can be started directly from the github.com UI. Of course, start from the fork branch.
• 
• If you need to start all jobs, either open a PR at https://github.com/graalvm/native-build-tools/pulls .
• Or temporarily modify the configuration file of Github Actions in the fork branch. This means deleting the content of this PR.

[dnestoro]

Both the current project and other projects I collaborate on use the Github Actions workflow_dispatch syntax in the CI configuration file, which means that a Job can be started directly from the github.com UI

Yes, you can trigger the workflow manually, but it won't pass the if statement you added in this PR, and therefore the job won't run, right?

The only way how you can run jobs on your fork is if you remove lines added in this PR, right?

[linghengqian]

Yes, you can trigger the workflow manually, but it won't pass the if statement you added in this PR, and therefore the job won't run, right?

The only way how you can run jobs on your fork is if you remove lines added in this PR, right?

• Yes, I misunderstood the role of workflow_dispatch. The related jobs will not be started.
• 
• To start the job, we can only manually remove the changes in the current PR in a new branch. Or, according to the general operation of the project in ASF, contributors will manually create a new CI file in the branch temporarily to test some large changes. Just like Build GraalVM Native Image nightly for ShardingSphere Proxy apache/shardingsphere#21109 (comment) described.