Issues

a single discord server cannot have more than 1000 users registered to it. A 1001th user attempting to register should get an error message. The message should tell them the server is full and to contact a server manager.

#25

· quarterback-ai-dev-environment opened

on Aug 22, 2026

the pricing page should have a card somewhere after the 3 tiers that mentions "if your community has different needs please contact us" just in case a user thinks none of the tiers work for their situation. It should be clear that they can reach out with custom requests.

#23

· quarterback-ai-dev-environment opened

on Aug 21, 2026

user should be able to click "pricing" in the navbar and reach a page that describes three different price tiers: 1. free tier. up to 10 users per server reporting status 2. cozy community tier. up to 50 users per server reporting status. $5 per month 3. large community tier. up to 250 users per server reporting status. $10 per month. this page should be informational only and should be well designed and easy to understand the available options

#21

· quarterback-ai-dev-environment opened

on Aug 21, 2026

a new release of this project must be created by tagging the latest commit with the version "v1.2.0" and pushing that tag to github.

#20

· quarterback-ai-dev-environment opened

on Aug 21, 2026

A manager of a discord server should be able to "remove" channel registration. Today they can register, and change the registered channel, but cannot remove registration entirely. I would like to add a "remove" button to the "reporting channel" section of the dashboard/server page. This button, when clicked, should open a confirmation modal. If the user confirms, then it should use htmx to call delete for that particular "discord_guild_settings" entry. If no channel is configured, the UI should say "not configured" and allow the user to click the "change" button. The rest of the workflow remains the same.

#18

· quarterback-ai-dev-environment opened

on Aug 21, 2026

the channel select dropdown on the dashboard/servers page should have a field at the top that allows you to filter the options in the dropdown, since some servers have many channels. There should also be a vertical limit to the dropdown of about 10 rows so that a server with 100 channels doesn't open a select box that takes up the whole vertical limit of the screen.

#16

· quarterback-ai-dev-environment opened

on Aug 21, 2026

the dashboard/server/:id page is very ugly. please use UI design best practices to rearrange the elements in a way that looks pleasant. Make sure to use DaisyUI components where possible. Please include screenshots in the PR so that the visual changes will be obvious.

#14

· quarterback-ai-dev-environment opened

on Aug 20, 2026

in ci.yml, two golang tools are installed using the @latest tag (staticcheck and govulncheck), but they should be pinned to a specific version to avoid an update to the tools causing a break in the build.

#11

· quarterback-ai-dev-environment opened

on Aug 20, 2026

gofmt is failing due to a recent change. please run gofmt and open a PR with any resulting changes

#9

· quarterback-ai-dev-environment opened

on Aug 20, 2026

need to run "go mod tidy" in order to make sure my requirements are up to date with the latest version. Please run "go mod tidy" and open a PR with the results.

#7

· quarterback-ai-dev-environment opened

on Aug 20, 2026

the project should run on the latest version of go (1.27). Please make sure there are no relevant breaking changes and upgrade this repository to use go 1.27. This includes any tooling used locally or via CI

#5

· quarterback-ai-dev-environment opened

on Aug 20, 2026

the CI github action should run "go test" as part of the workflow.

#3

· quarterback-ai-dev-environment opened

on Aug 20, 2026

Navigation Menu

Uh oh!

All issues

a single discord server cannot have more than 1000 users registered to it. A 1001th user attempting to register should get an error message. The message should tell them the server is full and to contact a server manager.

the pricing page should have a card somewhere after the 3 tiers that mentions "if your community has different needs please contact us" just in case a user thinks none of the tiers work for their situation. It should be clear that they can reach out with custom requests.

a new release of this project must be created by tagging the latest commit with the version "v1.2.0" and pushing that tag to github.

the dashboard/server/:id page is very ugly. please use UI design best practices to rearrange the elements in a way that looks pleasant. Make sure to use DaisyUI components where possible. Please include screenshots in the PR so that the visual changes will be obvious.

in ci.yml, two golang tools are installed using the @latest tag (staticcheck and govulncheck), but they should be pinned to a specific version to avoid an update to the tools causing a break in the build.

gofmt is failing due to a recent change. please run gofmt and open a PR with any resulting changes

need to run "go mod tidy" in order to make sure my requirements are up to date with the latest version. Please run "go mod tidy" and open a PR with the results.

the project should run on the latest version of go (1.27). Please make sure there are no relevant breaking changes and upgrade this repository to use go 1.27. This includes any tooling used locally or via CI

the CI github action should run "go test" as part of the workflow.

Uh oh!

Search results