#297 · Recognize canonical GitLab bounty links in wiki badges
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 #297 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.
Description
Wiki bounty-reference parsing currently recognizes the legacy GitLab hostname, while current issue links use git.juntogroups.org and work_items paths. Make references in new community pages visible to the existing bounty-badge pipeline.
Who might enjoy this
- Community interests: Community / knowledge sharing, Tech, Full stack
- Skills: backend, qa, docs
- Experience: starter; work style: analytical.
- Readiness: ready; bounty size: S (existing points tier; standard merge award stacks separately).
Current behavior and starting points
Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.
Relevant Files
Deliverables
- Accept canonical and legacy monorepo issue/work_items URLs with query or fragment suffixes; deduplicate IDs.
- Keep ordinary Markdown heading numbers and foreign-project URLs outside the recognized bounty references.
- Use the canonical GitLab host for the existing read-only issue lookup, preserving its timeout and graceful build behavior.
Dependencies and decisions
No prerequisite issue is required. Re-read current main and linked MRs before starting.
Acceptance criteria
- [ ] Add positive canonical and legacy URL cases, work_items cases, duplicates, foreign-project and ordinary #heading controls to the existing parser suite. Observe the canonical case fail before the change.
- [ ] Run pnpm --filter @irregularchat/wiki exec vitest run src/lib/bounties.test.ts; build the wiki and inspect a fixture page carrying one recognized bounty reference.
- [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
- [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.
Try it locally
Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:
Start with apps/wiki/src/lib/bounties.test.ts and a canonical issue URL copied from the bounty board. The pure parsing cases run without a GitLab token.
Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.
Out of scope
- No token rotation, new badge system, change to bounty award amounts or issue closure.
- Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.
For a coding agent and reviewer
Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.
A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.
Catalog index: #258.
<!-- community-interest-bounty:2026-10-18:wiki-canonical-bounty-refs -->
Relevant files
-
[apps/wiki/src/lib/bounties.ts](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/wiki/src/lib/bounties.ts)from issue -
[apps/wiki/src/lib/bounties.test.ts](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/wiki/src/lib/bounties.test.ts)from issue -
[apps/wiki/src/lib/bounty-pages.ts](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/wiki/src/lib/bounty-pages.ts)from issue
Hints
No hints yet.
Activity
No points have been awarded for this bounty yet.
Comments
Sign in to join the discussion.
No comments yet. Be the first to weigh in.