In the previous post, Using ChatOps to Improve the R&D Process, providing preview links for Pull Requests through ChatOps improved our agility. This post describes how to implement this feature quickly. 1. Step One: Configure a Trigger 1.1 Choose a Trigger GitHub has three kinds of Workflow triggers: scheduled, manual, and automatic.

1. Testing Is a Beacon at Sea The more complex and larger a project is, the more it demonstrates the value and importance of testing. Testing guarantees that the direction is right. Like a beacon appearing at sea while sailing, it can be used to check and correct the course, so the helmsman can stay aware of the situation at any moment and make adjustments.

1. What GitHub Actions Is In an earlier post I put the CI capabilities GitLab provides into practice — click here to see. The advantages of using GitLab are that it can be deployed privately, it allows an unlimited number of private repositories, its CI configuration is simple, and it can connect to self-hosted Runners.

1. Github Container Registry On September 1, GitHub announced that Github Container Registry had entered public beta, offering a free, unlimited-capacity Docker image registry service during the testing period. No more worrying about docker.io wiping images out of the blue. How nice, how sweet! GitHub is using hosted code repositories as its entry point and gradually covering the entire R&D toolchain to build a one-stop DevOps platform.

1. Create a merge commit PR commit log: 1 2 commit c1 commit c2 Integration branch commit log: 1 2 3 commit PR #NUM commit c2 commit c1 Create a merge commit carries every commit in the PR over to the integration branch intact, and adds one PR commit entry on top.