checkout VS minicli

checkout

To checkout the merged commit with actions/checkout on pull_request_target event, you need to get the pull request by GitHub API and set the merge commit hash to actions/checkout input ref.

If you re-run GHA after master changes, CI is testing over different code.

You can [disable](https://github.com/actions/checkout#checkout-pull-request-head-commit-instead-of-merge-commit) on the checkout action:

```

There was an outage yesterday too when the GitHub action “checkout@v3” broke when they released “checkout@v4”

Yes, they broke the ability for GitHub CI to checkout repos…

https://github.com/actions/checkout/issues/1448

The first two steps are setting up the job's environment. The checkout action will checkout out the repository at the triggering ref. The setup-python action will setup the desired Python runtime. My package supports Python 3.9+ so I'm targeting the minimum version for my build environments.

These first few steps demonstrate how you can run commands like npm install or import other workflows such as how it uses the actions/checkout to copy the contents of the repository into a working directory on the runner host. Read Reusable workflows for more about the syntax for referencing them.

Check out the repo: We will use the actions/checkout action to checkout the repository.

Take a look at the checkout action usage here https://github.com/actions/checkout

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.

{ "user": "Erika Heidi", "bio": "Software and Documentation Engineer", "projects": { "minicli/minicli": { "description": "CLI framework for PHP", "link": "https://docs.minicli.dev" }, "erikaheidi/autodocs": { "description": "Tiny framework for automating documentation", "link": "https://github.com/erikaheidi/autodocs/wiki" } } }

In case you didn't click on the link to intelephense, you should know that is a language server for php. If you just want to test the code I show here, you don't need the php interpreter installed, just the source code of a php project. You can use this repository: minicli, is a decent size codebase and doesn't depend on any other php libraries.

I've used Laravel Zero for several cli tools and I love it. The only thing that bugs me a bit is the size of the executable you end up with. For my next project I've decided to try out minicli, which is similar, but much smaller since it doesn't have any dependencies at all.

Let's create a simple demo app using Minicli, to demonstrate dependency management with Composer. The app will output a random combination of adjective + noun.

If you come across bugs or other problems while using or upgrading to Minicli 3, we'll appreciate if you can create an issue on GitHub so that me and other contributors can help address it. Thank you in advance!

We won't use specialised frameworks like Minicli or Laravel Zero because the goal is not so much to focus on features but to better understand the development, testing, and distribution phases of command-line programs.

This will create a new composer.json file and download the base minicli/minicli package. Next, you need to create the entry point script that runs your command. Using your code editor of choice, create a new file in the root of the application called minicli (or another name of your choice):

The action runs a single-command application created with Minicli, a minimalist command-line framework for building PHP CLI commands.

For this demo, we'll create a command-line application using Minicli, a minimalist framework for command line applications in PHP. We'll use the TwitterOAuth library to communicate with the Twitter API.