Skip to content

feat: add Tombstone to interested parties - #554

Merged
beeme1mr merged 1 commit into
open-feature:mainfrom
sairam0424:main
Aug 18, 2026
Merged

beeme1mr merged 1 commit into
open-feature:mainfrom
sairam0424:main

Conversation

@sairam0424

Copy link
Copy Markdown
Contributor

Tombstone is a self-hosted feature flag platform with an OpenFeature-compatible TypeScript provider.

The provider at packages/sdks/@flagmind/core/src/provider.ts implements:

  • All 4 typed resolvers (Boolean, String, Number, Object)
  • All 5 provider states (NOT_READY, READY, STALE, ERROR, FATAL)
  • No-throw guarantee on all resolvers

GitHub: https://github.com/sairam0424/Tombstone

@coderabbitai

coderabbitai Bot commented Jun 27, 2026 •

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c25b7be9-8cc3-4532-a8aa-8f618bd3b6af

📥 Commits

Reviewing files that changed from the base of the PR and between d857bd7 and 4a239ad.

📒 Files selected for processing (1)
  • interested-parties.md

📝 Walkthrough

Walkthrough

A new row for the Tombstone organization is added to the "Interested organizations" table in interested-parties.md, including its GitHub link and contact email support at tombstone.dev.

Interested Parties Update

Layer / File(s) Summary
Add Tombstone organization entry
interested-parties.md
Adds a single table row for Tombstone with its GitHub URL and support contact email.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly states the main change: adding Tombstone to the interested parties list.
Description check ✅ Passed The description is related to Tombstone, which matches the added interested party entry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Comment @coderabbitai help to get the list of available commands.

Warning

⚠️ This pull request has been flagged as potential spam (promotional) by CodeRabbit slop detection and should be reviewed carefully.

@jonathannorris

Copy link
Copy Markdown
Member

@beeme1mr
beeme1mr merged commit f4a66df into open-feature:main Aug 18, 2026
2 checks passed
sairam0424 pushed a commit to sairam0424/sairam0424 that referenced this pull request Sep 28, 2026
…mations

From a 3-way parallel /deep-research pass (elite-profile benchmarking,
GitHub Actions/widget mechanisms, and unsurfaced real signals for
sairam0424/kelvran/mcpsmiths) — implementing the 4 items that survived
cross-verification:

- Recent Highlights: added the real, merged open-feature/community#554 PR
  (verified merged_by=beeme1mr, an actual OpenFeature org maintainer) that
  added Tombstone to the CNCF-affiliated OpenFeature project's registry.
- New release-badge row (trelix, MindForge, Tombstone, RateCap) via
  shields.io — zero-config, dynamically live-updating. Deliberately
  excluded ag-bash: its GitHub "latest release" is a monorepo sub-package
  tag (cjs-consumer-example@1.3.3), not the main package version, so the
  badge would be misleading. Also skipped a GitHub Sponsors badge —
  confirmed via GraphQL (sponsorsListing: null) that Sponsors isn't
  enabled on this account.
- New "Recent Activity" section + .github/workflows/update-activity.yml,
  using jamesgeorge007/github-activity-readme (SHA-pinned, v0.5.0) to
  auto-populate recent Issues/PRs/Releases from the GitHub Events API —
  zero secrets beyond the default GITHUB_TOKEN, genuinely new content
  type vs. the existing RSS/snake/stats/LeetCode widgets.
- Track Record table converted from static to auto-updating: added
  scripts/update_track_record.py (recomputes all 4 numbers via `gh api`/
  GraphQL, matching the exact release-repo list and queries already
  verified live in prior rounds) plus
  .github/workflows/update-track-record.yml (weekly cron +
  workflow_dispatch, commits only if the numbers actually changed).
  Ran the script locally against live data as part of this change --
  it correctly picked up real drift since the last check (1,911->1,912
  merged PRs, 10.4K+->10.5K+ contributions), proving the automation
  works end-to-end before ever running in CI.

Explicitly not implemented (ruled out by research): a dependents.info
widget (live reverse-dependency checks found zero real dependents for
mindforge-cc/trelix/@ag-bash/bash — an empty widget would be worse than
no widget), and an animated contribution-graph transform (already exists
as the Platane/snk snake animation; a research-prompt oversight had it
missing from that agent's "already have" context).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants