Skip to content

docs(profile): refresh org profile claims - #18

Merged
hummbl-dev merged 2 commits into
mainfrom
docs/update-profile-projects
Jul 4, 2026
Merged

docs(profile): refresh org profile claims#18
hummbl-dev merged 2 commits into
mainfrom
docs/update-profile-projects

Conversation

@hummbl-dev

Copy link
Copy Markdown
Collaborator

Closes #13, Closes #14

  • Refreshes public HUMMBL profile claims to match current source-of-truth metrics.
  • Updates tests metric in header and hummbl-governance row.
  • Marks hummbl-transparency as private in the project table instead of linking as public.
  • Aligns FAQ claim line with updated test count.

Source: hummbl-dev/hummbl-governance README and private repo visibility check for hummbl-transparency.

@coderabbitai

coderabbitai Bot commented Jul 4, 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: ASSERTIVE

Plan: Pro Plus

Run ID: 0bb2c05e-ecc5-402c-8d74-d4d84711776f

📥 Commits

Reviewing files that changed from the base of the PR and between d2cd6c0 and 2cef3ee.

📒 Files selected for processing (1)
  • profile/README.md

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Updated the profile README governance test metrics from 550+ tests to 1970 collected tests.
    • Adjusted the transparency project entry to indicate the repository is private.
    • Refreshed the FAQ comparison text to match the updated test count.
    • Updated the FAQ heading formatting.

Walkthrough

The org profile README updates public test-count claims from 550+ to 1970, changes the hummbl-transparency project entry to private-repository wording, and adjusts the FAQ heading and answer text.

Changes

Org profile README updates

Layer / File(s) Summary
Profile claims refresh
profile/README.md
Updated the summary metrics, hummbl-governance table row, hummbl-transparency project entry, FAQ heading level, and FAQ answer text.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Poem

Hoppity hop, the README sings,
Fresh test counts and tidier things.
A private note, a FAQ tune,
The rabbit smiles at the doc’s bright moon. 🐰

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description covers the main changes, but it omits required template sections like Boundary, Source Status, Change Class, Evidence, and Notes. Add the missing template sections and fill in boundary, source status, change class, tests/checks run, receipt, and review notes.
Linked Issues check ⚠️ Warning #14 is addressed, but #13's required primitive-count and source-of-truth claim updates are not fully covered by the described changes. Update the primitive-count claims and add source-of-truth/evidence notes so the profile fully matches #13's acceptance criteria.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise and accurately summarizes the main profile documentation update.
Out of Scope Changes check ✅ Passed The changes stay within the profile README update and related docs cleanup, with no unrelated files or behavior introduced.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/update-profile-projects

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@profile/README.md`:
- Around line 9-19: The README markdown structure is invalid because the
Projects section skips a heading level after the top-level title and the
hummbl-transparency table row has a missing cell. Update the section heading
hierarchy under the README title so it follows proper markdown outline levels,
and make the hummbl-transparency entry in the Projects table match the same
three-column structure as the other rows. Use the `### Projects` heading and the
`hummbl-transparency` table row as the anchors when fixing this.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: de94f515-fd4b-4e49-ae68-1efcba025cb9

📥 Commits

Reviewing files that changed from the base of the PR and between cafbbfb and d2cd6c0.

📒 Files selected for processing (1)
  • profile/README.md

Comment thread profile/README.md Outdated
@hummbl-dev

Copy link
Copy Markdown
Collaborator Author

I triaged this as bot-reviewed CHANGES_REQUESTED with no requested reviewers, and only collaborator available is hummbl-dev (same as PR author), so non-author review cannot currently be requested via GitHub API. This appears blocked by repo collaborator policy; please add a non-author reviewer/collaborator if merge is urgent.

@hummbl-dev

Copy link
Copy Markdown
Collaborator Author

I triaged this as bot-reviewed CHANGES_REQUESTED with no requested reviewers. Repo collaborators are currently limited to hummbl-dev, so non-author review requests are effectively blocked by collaborator policy unless a qualifying reviewer is added. Please add a non-author reviewer/collaborator to unblock CHANGES_REQUESTED state if this PR is urgent.

Restores valid heading hierarchy and table shape in the org profile README.
@hummbl-dev
hummbl-dev merged commit 3778dea into main Jul 4, 2026
2 checks passed
@hummbl-dev
hummbl-dev deleted the docs/update-profile-projects branch July 4, 2026 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant