Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #13 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Submit a merge request that closes this issue to earn points on merge — bounties stack on the standard +40 merge_pr award. New to the repo? See the Contributing guide, and Local Development & SSO to run the app locally (cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.

Description

Status clarification

This bounty remains open. The existing !bounty command returns links; the work here is to add inline listings and issue lookup, with a shared client for both bots. The public Scoreboard JSON endpoint and board-discovery improvements are already implemented; those related merges do not complete this command expansion.

To claim: assign this issue to yourself and move it to status:in-progress on the Development board. Move to status:review when the MR is ready. A qualifying MR must include Closes #13; bounty points are recorded after merge and identity matching.

Current scope: expand the existing link-only handleBounty stub using the already available public Scoreboard JSON endpoint. Reuse one shared client/guard for both bots. Any personal assigned-work view must resolve verified linked identity through the server; a supplied email or display name is not identity. Add real-handler coverage for listing, lookup and unavailable service. Do not add a second GitLab discovery backend.

Earlier scope (historical; current qualification above takes precedence)

Context

The community-facing bot should surface open bounties so contributors can claim them without leaving Signal. Today, bounties live only on score.irregulars.io and GitLab — adding a !bounty command closes that loop and brings the bot ↔ scoreboard parity in line with !jobs, !events, !tasks.

Acceptance criteria

  • [ ] !bounty (no args) lists up to 10 unclaimed bounties with title, app, tier, points
  • [ ] !bounty <iid> shows full description and acceptance criteria for one issue
  • [ ] !bounty mine shows bounties assigned to the calling user (matched by email)
  • [ ] Output uses Signal's text formatting (bold for title, monospace for app name)
  • [ ] Caches GitLab API response in Redis for 5 min to avoid rate-limit churn

Technical hints

  • !bounty already exists as a link-only stub: handleBounty in selfhost/messaging-apps/signal-messenger/src/src/bot/command-handler.ts (dispatched from the switch as !bounty/!bounties). Expand it to list inline; handleJobSearch in the same file is the closest listing pattern.
  • For the data source, wrap GET on score.irregulars.io if a JSON endpoint is added there, otherwise direct GitLab API. Put the client in packages/shared-utils/src/bot-utils/ (alongside career-board-client.ts) so both bots can share it.
  • Add an isBountyConfigured() guard in packages/shared-utils/src/bot-utils/ following the same pattern as isCareerBoardConfigured()

Related

  • Bounty page on scoreboard: https://score.irregulars.io/bounties
  • GitLab issues API: https://docs.gitlab.com/ee/api/issues.html

--- *Submit a merge request that says Closes #<this issue iid> in the description. On merge to main, the GitLab webhook will auto-award your bounty + the standard merge_pr (40 pts) to your scoreboard account. Email on commit must match your Authentik email.*

<!-- bounty-reconciled:2026-10 -->

Relevant files

No relevant files linked yet.

Hints

No hints yet.

Activity

No points have been awarded for this bounty yet.

Comments

No comments yet. Be the first to weigh in.

↑ Top