I'm Not on the DEV Team. I Still Debugged Their Missing Badges From Public Code. (And My First Test Was Wrong.)
I’m not on the DEV team. I don’t have an admin panel, production database access, or internal Slack....
First seen by Oriel on .
AI summary
A contributor traced missing multi-commit badges in Forem to badge slug mismatches and fixed badge awarding to include context messages, avoid duplicate attempts, and log missing configuration appropriately.
- The hourly worker resolved hardcoded badge slugs against the database; four multi-commit slugs did not match stored badge records, so those tiers were skipped.
- PR #24113 added context messages, switched badge creation to first_or_create, and deferred slug lookup until after checking GitHub authentication.
- A review changed per-slug warning logs to one informational message per run because many self-hosted Forem communities lack DEV-specific badge records.
- The initial idempotency spec also passed on main because uniqueness validation masked duplicate creation; enabling allow_multiple_awards made the regression test expose the bug.
- All 34 checks passed, and the fix was merged as d1b962e; the author then received the 4x DEV Contributor Club badge.
#forem #ruby on rails #automated testing #observability
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Reactions
Total public reactions reported by the source; distinct from points and likes.
- DEV Community: 139, latest observation ; +123 over observed period since
Comments
Comment count reported by the source.
- DEV Community: 64, latest observation ; +57 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| DEV Community | 4911807 | https://dev.to/dj29/im-not-on-the-dev-team-i-still-debugged-their-missing-badges-from-public-code-and-my-first-test-18oo Read discussion |