ops: create bugbot Forgejo account; wire in-app feedback buttons to post as bugbot not alan #118

New issue

Open

opened 2026-06-01 15:50:21 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-06-01 15:50:21 -07:00

Owner

Problem

All three products (Peregrine, Kiwi, Snipe) have in-app feedback buttons that file Forgejo issues. They currently submit as Alan's personal account. Testers (especially non-technical beta testers recruited via Reddit) will see the account name on filed issues, and it shouldn't be a personal account.

What to do

Create a bugbot Forgejo account (or cf-bugbot) on git.opensourcesolarpunk.com
Generate a bot token for that account
Update the feedback button endpoint in each product to use the bot token instead of Alan's token
Confirm the bot account has write access to issues on peregrine, kiwi, and snipe repos
Test end-to-end: submit feedback in-app, confirm issue appears filed as bugbot

Products affected

Peregrine
Kiwi
Snipe

Why it matters

We're about to do public beta tester calls. If someone files feedback and sees it posted under a personal account, it's confusing and unprofessional. Bot account makes it clear it's automated and keeps Alan's personal account off public-facing issue threads.

## Problem All three products (Peregrine, Kiwi, Snipe) have in-app feedback buttons that file Forgejo issues. They currently submit as Alan's personal account. Testers (especially non-technical beta testers recruited via Reddit) will see the account name on filed issues, and it shouldn't be a personal account. ## What to do 1. Create a `bugbot` Forgejo account (or `cf-bugbot`) on git.opensourcesolarpunk.com 2. Generate a bot token for that account 3. Update the feedback button endpoint in each product to use the bot token instead of Alan's token 4. Confirm the bot account has write access to issues on peregrine, kiwi, and snipe repos 5. Test end-to-end: submit feedback in-app, confirm issue appears filed as bugbot ## Products affected - Peregrine - Kiwi - Snipe ## Why it matters We're about to do public beta tester calls. If someone files feedback and sees it posted under a personal account, it's confusing and unprofessional. Bot account makes it clear it's automated and keeps Alan's personal account off public-facing issue threads.