Jason Garber<p>Okay, so I just managed to push a new <a href="https://indieweb.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ruby</span></a> gem release to <a href="https://indieweb.social/tags/RubyGems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RubyGems</span></a> with attestation from <a href="https://indieweb.social/tags/Codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Codeberg</span></a> through <a href="https://indieweb.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHub</span></a>.</p><p>The source repository uses Codeberg's source control, Issues, Pull Requests, Releases, and Actions. A <a href="https://indieweb.social/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Forgejo</span></a> Actions workflow will run on a new published release that pushes a “repository dispatch" event to a repository on GitHub that clones the source repository and publishes to RubyGems.</p><p>I'm… amazed it works.</p>