2 KiB
2 KiB
Changelog
2026-06-08
Added
- Community panel added to the test portal.
- Discord card added.
- Discord icon added.
- Discord invite link configured.
- Discord Integration project folder created.
Changed
- Portal layout adjusted to reduce negative space.
- Knowledge Base, Development, and Community now align better.
Verified
- Discord icon displays correctly.
- Discord invite opens successfully.
- Test portal remains operational.
Planned
- Forgejo to Discord changelog automation.
- #recent-activity Discord channel.
- Authentik integration.
- GitHub coming soon card.
- Role-based onboarding.
Recent Activity Feed Plan
Added
- Renamed planned Discord live feed from #change-log to #recent-activity.
- Defined #recent-activity as the live activity feed for KiteStacks.
- Documented that changelog details should link back to Forgejo documentation.
Channel Purpose
#recent-activity will show short updates about what changed.
Each important update should include:
- What changed
- Why it changed
- Where the documentation lives
- Whether it affects users
2026-06-11
Added
- Forgejo push webhooks configured on kitestacks-homelab, OSTicketSystem, hyprland-desktop-t14s, and kitestacks-homelab-autosync-test, posting to the Discord #recent-activities channel.
- Each Discord message includes a clickable link back to the Forgejo repository/commit (gitforge.kitestacks.com).
Verified
- Test delivery succeeded on all 4 repo webhooks.
- This commit serves as the first real push-event test of the integration.
Fixed
- Discord deliveries were silently failing for every webhook: each
webhook's
metaconfig was empty, which broke Forgejo's Discord payload builder (invalid JSON, then Discord rejected the emptyusernamefield). Set a validusername("KiteStacks Forgejo") on all 4 webhooks. - Re-ran test deliveries on all 4 repos - all returned 204 from Discord.
- This push is the first real end-to-end delivery confirming #recent-activities now receives live Forgejo push notifications.