Repository navigation
chore: add FUNDING.yml so the Sponsor button resolves from this repo - #11
Conversation
Mirrors the org config from TheIntroDB/.github so the repository shows the GitHub Sponsors button on its own.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Add funding account .github/FUNDING.yml |
The funding configuration lists TheIntroDB as a GitHub funding account. |
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Other
Merge Risk: 
Minimal · up to cb06b
-
The repository-level Sponsor configuration is ready to merge.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Why
The org's Sponsors config lives in TheIntroDB/.github, but that org-default file is only picked up for repos that don't declare their own — and the Sponsor button people see while browsing an integration repo is resolved from that repo. Anyone who lands on this repo from the plugin listing has no in-place way to sponsor.
What the PR does
Adds
.github/FUNDING.ymlat the canonical per-repo location (.github/FUNDING.yml), byte-identical to the org file:Deliberately no other changes — no code, workflows, issue templates, or docs are touched, so there is nothing to review beyond the one-line config.
Notes
TheIntroDB/.github/FUNDING.yml; if the org config changes, update this copy too (or keep them in sync via a workflow).Summary by CodeRabbit