<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GHES on Ely Clover</title><link>https://stg.elyclover.com/categories/ghes/</link><description>Recent content in GHES on Ely Clover</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>kevin@elyclover.com (Kevin Holmes)</managingEditor><webMaster>kevin@elyclover.com (Kevin Holmes)</webMaster><copyright>© 2026 Kevin Holmes</copyright><lastBuildDate>Fri, 28 Jul 2023 10:00:00 +0000</lastBuildDate><atom:link href="https://stg.elyclover.com/categories/ghes/index.xml" rel="self" type="application/rss+xml"/><item><title>Governance of 3rd party GitHub Actions in GHES instances</title><link>https://stg.elyclover.com/posts/governance-of-3rd-party-gh-actions/</link><pubDate>Fri, 28 Jul 2023 10:00:00 +0000</pubDate><author>kevin@elyclover.com (Kevin Holmes)</author><guid>https://stg.elyclover.com/posts/governance-of-3rd-party-gh-actions/</guid><description>&lt;p&gt;After spending a few years using GitHub Actions in Open Source, Commercial, and FedRamp environments, I wanted to share some of my takeaways for a few options on how to provide governance over what Actions you allow to be used within your self-hosted GHES and Actions runner instances. This article will focus on government or commercial users self-hosting source code (GHES) and the Actions runners in their secured environments.&lt;/p&gt;
&lt;p&gt;There are two paths if you boil this down:&lt;/p&gt;</description></item></channel></rss>