<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Meercode on Medium]]></title>
        <description><![CDATA[Stories by Meercode on Medium]]></description>
        <link>https://medium.com/@meercode?source=rss-3231ac5d0866------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bfMTp3zOSanXO8adDLjunQ.jpeg</url>
            <title>Stories by Meercode on Medium</title>
            <link>https://medium.com/@meercode?source=rss-3231ac5d0866------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:14:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@meercode/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building and Monitoring Your First Github Actions Workflow]]></title>
            <link>https://medium.com/bitsrc/building-and-monitoring-your-first-github-actions-workflow-b9cad4a1014d?source=rss-3231ac5d0866------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9cad4a1014d</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ci-monitoring]]></category>
            <category><![CDATA[github-actions]]></category>
            <dc:creator><![CDATA[Meercode]]></dc:creator>
            <pubDate>Thu, 29 Oct 2020 20:18:55 GMT</pubDate>
            <atom:updated>2020-10-29T20:18:55.289Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZ_jv-xjX_FfJR5fQH_6UQ.png" /></figure><p><strong>Github Actions</strong> is Github’s native solution to CI/CD, which is available to the developer’s community since it was launched in 2019.<strong> Action’s </strong>simple, flexible, and affordable nature made many teams migrate from existing <em>CI/CD </em>solutions to unlock the endless possibilities of the new platform.</p><p>My team has been of the early adopters of<strong> Github Actions</strong>. As a group of highly <em>Javascript</em> focused developers, we were able to automate tens of pipelines for our frontend and backend projects. Thanks to <em>Javascript/Typescript</em> support of the platform, we created many <strong>Actions</strong> (like <em>plugins</em> in traditional build tools) to extend the functionality according to our needs.</p><p>After 1 year of experience with Github Actions, we discovered the following advantages of the tool in comparison to former CI/CD solutions we tested:</p><ul><li>Zero management costs (no need for any agents or master nodes)</li><li>Easy to learn and master</li><li>You can keep your workflows in your source code</li><li>A rich <strong>Action</strong> (plugin) library. It’s easy to develop your custom <strong>Actions</strong>.</li><li>Sensible pricing model: 3000 free minutes for premium users of private repositories. Public repositories are completely free!</li><li>It has a rich action library and it is very easy to develop your actions.</li><li>Supports <em>Linux</em>, <em>Windows</em>, and <em>macOS</em> platforms. (<em>macOS</em> support is a rare feature among competitors)</li><li>With a self-hosted runner, it’s possible to run a free version on your own infrastructure.</li></ul><p>A minor disadvantage of the platform was the lack of monitoring tools you can watch the status of your workflows. The problem got bigger with the increasing number of repositories and pipelines we had to manage. In the end, we decided to develop our own dashboarding solution.</p><p>It started as a <em>React</em> frontend and <em>NestJS</em> backend to consume relevant Github API’s and display it in a clean way. The tool was appreciated among our team members and we continued developing new features.</p><p>Recently we released our dashboarding tool as <strong>SaaS</strong> project and started a public beta program to share it with the developer’s community. If you are interested, you can read more about Meercode’s <a href="https://dev.to/pankod/public-beta-meercode-a-beautiful-dashboard-and-monitoring-tool-for-github-actions-466g">story on this blog post </a>or visit <a href="http://meercode.io/">meercode.io </a>to try the product.</p><p>To demonstrate how you simply create your workflows on Github Actions, we want to go over a real-life example.</p><p>The task is simple. For one of our repositories on Github, we wanted an <a href="https://appcenter.ms/">AppCenter</a> build to be triggered whenever a pull request is made. Fortunately, AppCenter has a public REST API we can use to start the builds.</p><p>The action we are going to create should be triggered when</p><ol><li>A pull request is opened or re-opened,</li><li>Unit tests are passing.</li></ol><p>If all conditions are met, we’ll start the build on the AppCenter. So let’s start creating our action.</p><p>From your repository on GitHub, create a new file in the .<em>github/workflows</em> directory named <em>app_center_pull_request.yml.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iyCUtUXoh8MF11Rm" /></figure><p>We give our action the name “Pull Request Opened [App]” by using the <strong>“name:”</strong> attribute.</p><p>To get our action triggered on pull requests we are going to use native Github workflow events. You can configure workflows to run for one or more events using the <strong>“on:”</strong> syntax. A complete list of workflow events you can use in your actions is documented on this <a href="https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows">reference page.</a></p><p>In the next step, we are going to tell our action what to do when the “<em>pull_request</em>” event is triggered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*upqVeOmReybteXcC" /></figure><p>Under the “<strong>jobs:</strong>” attribute, we can add an arbitrary number of jobs to run. We label our first job with <strong>“build:” </strong>attribute and configure it as seen above.</p><p><strong>“runs-on:” </strong>and <strong>“matrix:”</strong> attributes specify the environment the action will run on. “<strong>steps</strong>:” will define the synchronous steps:</p><ul><li>The first step makes use of <a href="https://github.com/mdecoleman/pr-branch-name">another action</a> from “Actions Marketplace”. It retrieves <em>“pull request name” </em>that we can use in the next steps.</li><li>In the second step, we’ll init our app and run the tests. The action will proceed to the next step if the tests run successfully.</li><li>Now, we’ll configure the build for the corresponding branch name by calling the <em>AppCenter API </em>with a curl command. We are using the branch name from the first step to build the <em>URI </em>of the relevant branch.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Pppq6J46U6HfxvIS" /></figure><ul><li>Finally, we trigger a build for both iOS and Android versions of the application:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jazO_rGHuFgFg4y0" /></figure><p>To run and test your workflow, just open a pull request. This will trigger and run the action automatically. To view the results, you can go to the <strong>“Actions”</strong> tab of the repository and select your workflow and the corresponding run.</p><p>If you go deeper with Github Actions and start to manage a lot of workflows in multiple repositories, you are always free to try the dashboarding solution <a href="https://meercode.io/">Meercode</a> we mentioned before.</p><h3>Learn More</h3><ul><li><a href="https://blog.bitsrc.io/publishing-your-deno-modules-using-github-f2bd86173392">Publishing your Deno modules using GitHub</a></li><li><a href="https://blog.bitsrc.io/what-are-github-actions-and-how-to-use-them-e89904201a41">What are GitHub Actions and How to Use Them</a></li><li><a href="https://blog.bitsrc.io/github-actions-how-to-deploy-angular-app-to-firebase-hosting-89a93f9c4fe1">Github Actions: How to deploy Angular App to Firebase Hosting</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9cad4a1014d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitsrc/building-and-monitoring-your-first-github-actions-workflow-b9cad4a1014d">Building and Monitoring Your First Github Actions Workflow</a> was originally published in <a href="https://medium.com/bitsrc">Bits and Pieces</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>