# GitHub Action voor het aanmaken van topics bij gepubliceerde releases

**URL:** https://meta.discourse.org/t/github-action-for-creating-topics-on-published-releases/221114
**Category:** Extras
**Created:** [16 maart 2022 om 14:41 UTC](https://meta.discourse.org/t/github-action-for-creating-topics-on-published-releases/221114 "2022-03-16T14:41:09Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![benword](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/benword/32/493782_2.png) [@benword](https://meta.discourse.org/u/benword)
#### Post date: [12 maart 2026 om 00:06 UTC](https://meta.discourse.org/t/github-action-for-creating-topics-on-published-releases/221114/3 "2026-03-12T00:06:08Z")

</div>

Heads up: `v1.1.0` was just released with GitHub-to-Discourse username mapping

This is useful for projects with multiple maintainers. Release topics can now be posted as the release author’s mapped Discourse username, instead of always using a fixed `discourse-author-username` (or `system` as fallback).

Details are in the README, but the mapping comes from a `discourse.yml` file in your org’s `.github` repository.

When working on this update, I noticed some of y’all have been using it ❤

- Jenkins uses it: [Blog & News - Jenkins](https://community.jenkins.io/c/blog/23)
- NetBird uses it: [Topics tagged releases](https://forum.netbird.io/tag/releases)
- Aleph uses it: [Topics tagged release](https://aleph.discourse.group/tag/release/2)

---

_[View the full topic](https://meta.discourse.org/t/github-action-for-creating-topics-on-published-releases/221114)._