Skip to content

Add the adamXbot project status hub - #1

Merged
adamXbot merged 1 commit into
mainfrom
feat/project-status
Aug 9, 2026
Merged

Add the adamXbot project status hub#1
adamXbot merged 1 commit into
mainfrom
feat/project-status

Conversation

@adamXbot

@adamXbot adamXbot commented Aug 8, 2026

Copy link
Copy Markdown
Owner

The adamXbot half of the portfolio status system. Its own status.json, its own badges, its own token — nothing reaches across accounts.

Draft until gh-workflows#7 is merged and v1 retagged, since the workflow calls privacykey/gh-workflows/.github/workflows/project-status.yml@v1.

What changed

profile/README.md's hand-written project list is replaced by a generated one. The old list covered 7 of 22 repos, said nothing about whether any were still maintained, and had no way to stay true. The new one is rendered expanded (not collapsed) because on an org profile the project list is the page.

Needs a secret

STATUS_TOKEN — a fine-grained, read-only PAT scoped to adamXbot only. Without it the build still runs; only the drift check is skipped, and it says so rather than reporting private repos as healthy.

Tiers

🟢 Active 1 · 🚧 Building 5 · 🛡️ Maintained 3 · 📦 Parked 7 · ⚠️ Unmaintained 3 · 🍴 Fork 3 — 9 of 22 listed publicly.

Two flagged for fixing: the tap serves BananaBlitz 0.0.2 against a v0.0.3 release (112 days stale), and wwav's only release is a draft.

🤖 Generated with Claude Code

status.json is the single source of truth for every adamXbot repo's maintenance
tier. The badges, STATUS.md and the profile project list are all generated from
it by the shared workflow in privacykey/gh-workflows.

Replaces the hand-maintained project list on the profile. That list covered 7 of
22 repos, said nothing about whether any of them were still being worked on, and
had no mechanism to stay true.

Badges are generated for public, listed repos only — the badges directory is
browsable, and one file per repo would publish an index of unreleased work.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@adamXbot
adamXbot marked this pull request as ready for review August 8, 2026 14:54
@adamXbot
adamXbot merged commit 65c7593 into main Aug 9, 2026
@adamXbot
adamXbot deleted the feat/project-status branch August 9, 2026 09:13
adamXbot added a commit to adamXbot/homebrew-tap that referenced this pull request Aug 10, 2026
* docs: restructure the README to the portfolio standard

Reorders the README into the shared infrastructure-repo layout: what the
tap serves and who consumes it, how a consumer uses it, the version
contract, and how to change it without breaking downstream.

Adds the project-status badge and the fenced disclosure block. The badge
currently renders "resource not found" because the adamXbot status hub
(adamXbot/.github#1) has not merged yet; the endpoint path is correct.

Corrections:

- Dropped the claim that the apps "are currently not notarized". The
  BananaBlitz release workflow signs and notarises the DMG, so the blanket
  statement is not verifiable from this repo. The xattr instructions stay,
  described as what the cask's postflight and caveats actually do.
- Replaced "applications developed by adamxbot" (plural) with the single
  cask this tap actually contains.
- Records that Casks/bananablitz.rb pins 0.0.2 while BananaBlitz v0.0.3 is
  the latest release, that no automation opens bump PRs here, and that the
  bump is a separate change. The cask is not touched by this commit.
- States that there is no CI on main today and links the open PR that
  proposes a syntax gate, rather than implying checks exist.

Nothing was removed: the tap, install, and Gatekeeper-warning content from
the previous README is all still here. 723 -> 4158 bytes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* Correct the closing paragraph about tap quietness

The paragraph was carried over from privacykey/homebrew-tap, where it is true.
Here it is not: bananablitz.rb pins 0.0.2 while v0.0.3 shipped in April, so the
cask does not match its upstream release and anyone installing from this tap
gets an older build. It also asserted the repo is healthy, which contradicts
the status badge.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Co-authored-by: Adam Kostarelas <ha@adam.kostarelas.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.

1 participant