toolkit VS setup-java

Different libraries (like actions/toolkit and microsoft/azure-pipelines-task-lib) with more accessible and easy-to-use APIs are available out-of-box

I used the libraries from actions/toolkit to create my action. It's more comfortable than when I did it with Docker. I looked at all the libraries, and most of all: actions/core, actions/exec and actions/github.

The Action is built using TypeScript and Node.js, popular choices for GitHub Actions due to their excellent support for asynchronous operations, a crucial requirement considering the multiple I/O operations involved. In the initial setup, I used the actions/toolkit package which provides useful utilities to streamline the creation of GitHub Actions. I picked @actions/core for basic functionalities such as inputs, outputs, and error handling, @actions/github to interact with GitHub's REST API, and @actions/exec to execute shell commands.

The package @actions/github provides a hydrated Octokit.js client. Octokit.js is the SDK of GitHub and contains several subpackages like @octokit/rest and @octokit/graphql to interact with the REST or GraphQL API.

The GitHub Action was implemented with TypeScript using the GitHub Actions Toolkit and the OpenAI Node.js Library. The Action is activated on new comments on issues and pull requests if they mention @AdaGPT. The relevant issue number is determined from the event payload. Then all existing comments for this issue are read. If the issue is a pull request, the git diff is also read.

Creating actions can be an overwhelming task, so to help you on your journey, here are two indispensable resources that can assist you in getting started; Actions Toolkit and Javascript action template. Still, this article will dive into how to create an action.

Please support something like "allow-failure" for a given job

More than 2 years of ignoring requests to add an important feature (allow-failure) to Github Actions (ref, ref. When not ignoring, completely misunderstanding the feature as if those building Github Actions are unfamiliar with core features of competing platforms.

Then, we have two important initial steps to define. The first one is an official GitHub Action used to check-out a repository so a workflow can access it. The second one it's pretty more complex but, briefly, downloads and set up a requested version of Java.

The most popular ones are Node.js, Python, Java JDK, Go, .Net Core SDK.

Finally, note that the v2 of setup-java GitHub Action limits the possible JDK distributions to four options. If you need to use one that is not listed, use foojayio/setup-java instead to configure any distribution.

See https://github.com/actions/setup-java for more configuration regarding distribution, version and caching.

Why can't Oracle just integrate with https://github.com/actions/setup-java like everyone else?

Next up we'll need to add a step to compile our production ready build. For this we can add two new steps, one which configures our Node version to ensure it matches our application, followed by another that runs the necessary commands with npm. Depending on how your application is built you may need to add another step between these to install any sort of required environments such as Python or Java.

Set up the JDK with the actions/setup-java GitHub Action.

It now works (as of yesterday) with Github Actions via https://github.com/actions/setup-java and setting the distribution to temurin.

The Kotlin compiler needs Java to be present, so we use a predefined GitHub Action to install Java 1.8.