<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>GitHub on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/github/</link><description>Recent content in GitHub on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Sat, 12 Aug 2023 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/github/atom.xml" rel="self" type="application/rss+xml"/><item><title>Zero-Cost Service Availability Monitoring with Upptime</title><link>https://www.chenshaowen.com/en/blog/monitor-service-accessibility-with-upptime-for-free.html</link><pubDate>Sat, 12 Aug 2023 00:00:00 +0000</pubDate><atom:modified>Sat, 12 Aug 2023 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/monitor-service-accessibility-with-upptime-for-free.html</guid><description>1. What Needs Dial Testing GPT was all the rage this year, and I deployed and developed several applications and mini programs to learn from. Of course, following the principle of helping vendors test their features, right now only the GPT 3.5 API costs a little every day — the</description><dc:creator>微信公众号</dc:creator><category>GitHub</category><category>Actions</category><category>Monitoring</category><category>Dial Testing</category><category>Operations</category><category>Learning</category><category>Availability</category><category>Free</category><category>CICD</category><category>Best Practices</category></item><item><title>Developing a WeChat Official Account Backend with Tencent Cloud Serverless</title><link>https://www.chenshaowen.com/en/blog/develop-a-wechat-backend-using-tencent-serverless.html</link><pubDate>Sat, 28 Aug 2021 00:00:00 +0000</pubDate><atom:modified>Sat, 28 Aug 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/develop-a-wechat-backend-using-tencent-serverless.html</guid><description>1. Where Serverless Fits If cloud computing is meant to make resources flow like tap water — turn it on and use it, turn it off and it stops — then Serverless is one of the future directions of cloud computing. Compared with runtimes such as IaaS and Kubernetes, Serverless</description><dc:creator>微信公众号</dc:creator><category>GitHub</category><category>CICD</category><category>Serverless</category><category>WeChat</category><category>R&amp;D</category><category>Operations</category></item><item><title>10 Advanced GitHub Actions Tips You Should Know</title><link>https://www.chenshaowen.com/en/blog/10-tips-of-github-action.html</link><pubDate>Sun, 31 Jan 2021 00:00:00 +0000</pubDate><atom:modified>Sun, 31 Jan 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/10-tips-of-github-action.html</guid><description>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.</description><dc:creator>微信公众号</dc:creator><category>GitHub</category><category>GitHub Actions</category><category>CICD</category><category>DevOps</category><category>R&amp;D</category></item><item><title>GitHub Actions Online Debugging Tool: debugger-action</title><link>https://www.chenshaowen.com/en/blog/a-debugger-for-actions.html</link><pubDate>Mon, 18 Jan 2021 00:00:00 +0000</pubDate><atom:modified>Mon, 18 Jan 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/a-debugger-for-actions.html</guid><description>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&amp;rsquo;s repository, to improve its continuous build setup.</description><dc:creator>微信公众号</dc:creator><category>GitHub</category><category>Actions</category><category>DevOps</category><category>CICD</category><category>demo</category></item><item><title>GitHub Actions: Build a ChatOps System in Three Steps</title><link>https://www.chenshaowen.com/en/blog/using-github-actions-to-build-a-chatops-in-three-steps.html</link><pubDate>Wed, 06 Jan 2021 00:00:00 +0000</pubDate><atom:modified>Wed, 06 Jan 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/using-github-actions-to-build-a-chatops-in-three-steps.html</guid><description>In the previous post, Using ChatOps to Improve the R&amp;amp;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.</description><dc:creator>微信公众号</dc:creator><category>GitHub</category><category>GitHub Actions</category><category>R&amp;D</category><category>DevOps</category><category>ChatOps</category></item><item><title>How to Add Your Own Runner Hosts to GitHub Actions</title><link>https://www.chenshaowen.com/en/blog/how-to-add-self-hosted-runners-to-github-action.html</link><pubDate>Fri, 04 Dec 2020 00:00:00 +0000</pubDate><atom:modified>Fri, 04 Dec 2020 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/how-to-add-self-hosted-runners-to-github-action.html</guid><description>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.</description><dc:creator>微信公众号</dc:creator><category>GitHub</category><category>GitHub Actions</category><category>CICD</category><category>DevOps</category><category>Tools</category><category>R&amp;D</category><category>Operations</category></item><item><title>Jenkins Integrated GitHub Development</title><link>https://www.chenshaowen.com/en/blog/jenkins-integrated-github-development.html</link><pubDate>Tue, 18 Jul 2017 21:29:41 +0000</pubDate><atom:modified>Tue, 18 Jul 2017 21:29:41 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/jenkins-integrated-github-development.html</guid><description>1. Basic Concepts Continuous Integration Continuous integration emphasizes that once developers commit new code, a build and (unit) test run immediately. From the test results we can determine whether the new code and the existing code integrate correctly. Continuous Delivery Building on continuous integration, continuous delivery deploys the integrated code</description><dc:creator>微信公众号</dc:creator><category>Tools</category><category>Development</category><category>Jenkins</category><category>GitHub</category><category>CI</category><category>DevOps</category><category>R&amp;D</category></item></channel></rss>