1. A Confusing Problem 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 name: Go on: [push, pull_request] jobs: build: name: CI runs-on: ubuntu-latest steps: - name: Set up Go 1.13 uses: actions/setup-go@v1 with: go-version: 1.13 - name: Check out code into the Go module directory uses: actions/checkout@v2 - name: Check pr is properly formatted run: diff -u <(echo -n) <(gofmt -d .

If you already use GitHub Actions, this article will show you more interesting and useful ways to use it. By the time I finished writing, I had added several more workflows to my repositories. 1. Passing Parameters When a Workflow Runs When a workflow runs, you can allow parameters to be entered on the GitHub Actions page to control the execution logic.

1. Log in to Ngrok and get an Authtoken 1.1 Log in to the Ngrok website and get an Authtoken Visit the Ngrok website, https://dashboard.ngrok.com/ , and log in with a GitHub or Google account. Go to the Authentication page and find your Authtoken, as shown below: 1.2 Configure Secrets under the GitHub project On the project’s Settings page, add a new Secret, as shown below:

1. What Is Ngrok Ngrok is an intranet penetration tool that can publish services on the internal network to the public internet. The figure below illustrates its function well: Compared with a similar tool like Frp (which requires running both a Server and a Client), Ngrok turns intranet penetration into

1. Debugging Until You Want to Quit GitHub Actions is the continuous integration service GitHub launched in October 2018. For open-source projects it offers unlimited free build time, and it supports Linux, MacOs, and Windows systems, which makes it very appealing. But a recent experience changed my view. I submitted a commit, improvement: build and ci, to a colleague’s repository, to improve its continuous build setup.