<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitHub Actions on Coderrob</title><link>https://coderrob.com/tags/github-actions/</link><description>Recent content in GitHub Actions on Coderrob</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 20 Feb 2025 22:49:06 -0600</lastBuildDate><atom:link href="https://coderrob.com/tags/github-actions/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Actions: GitHub API Rate Limit Check Action</title><link>https://coderrob.com/posts/github-actions-github-api-rate-limit-check-action/</link><pubDate>Thu, 20 Feb 2025 22:49:06 -0600</pubDate><guid>https://coderrob.com/posts/github-actions-github-api-rate-limit-check-action/</guid><description>&lt;p&gt;GitHub Actions doesn&amp;rsquo;t (seem to?) provide built-in insights into API rate limits, making it difficult to diagnose runtime failures caused by hitting request limits.&lt;/p&gt;
&lt;p&gt;To address this, I created a reusable GitHub Action that proactively logs GitHub current limit, the max limit, and the next reset time in UTC.&lt;/p&gt;
&lt;p&gt;This GitHub Action provides an automated, real-time check of your repository’s GitHub API rate limits, giving you instant visibility into your API consumption. With detailed reporting and proactive alerts, you can prevent unexpected disruptions and optimize API usage in your workflows.&lt;/p&gt;</description></item><item><title>Streamlining GitHub Actions Development with Self-Documenting GitHub Actions</title><link>https://coderrob.com/posts/streamlining-github-actions-development-with-self-documenting-github-actions/</link><pubDate>Wed, 05 Feb 2025 08:57:23 -0600</pubDate><guid>https://coderrob.com/posts/streamlining-github-actions-development-with-self-documenting-github-actions/</guid><description>&lt;p&gt;In my recent project, I&amp;rsquo;ve focused on streamlining the development workflow for Cisco Collaboration by migrating thousands of repository build processes to GitHub Actions. This transition has brought numerous benefits in terms of automation and efficiency, but it also presented a challenge &lt;strong&gt;in keeping in-development GitHub Action documentation up-to-date&lt;/strong&gt; and ensuring consistency across all actions.&lt;/p&gt;
&lt;p&gt;One area that became a repetitive drain on productivity was documenting actions, specifically details like inputs, outputs, environment variable usage, and other metadata values of interest. &lt;strong&gt;The lack of consistency was the only consistency&lt;/strong&gt;; every existing and even newly created action had either no documentation, or had its own unique way to document the action.&lt;/p&gt;</description></item></channel></rss>