chore: add a repo-level FUNDING.yml

[shenxianpeng]

Requested by Xianpeng · project thread

Summary

Before: this repo has no FUNDING.yml of its own and relies on the org-level one in cpp-linter/.github. ecosyste.ms showed empty funding_links for cpp-linter-action in the same situation, so dependency-based funds that pay through each repo's own FUNDING.yml (such as ecosyste.ms Funds) may not know where to send money for this project.

After: .github/FUNDING.yml in this repo lists the Open Collective, the same file cpp-linter/cpp-linter-action#498 added. The Sponsor button on this repo shows Open Collective only, matching the README's Sponsors section.

How: one file, open_collective: cpp-linter. GitHub Sponsors is left out until the org's Sponsors profile is live; add github: cpp-linter then. That ecosyste.ms ignores the org-level file is inferred from the empty funding_links, not confirmed in its source.

Related Issues

Relates to cpp-linter/cpp-linter-action#498.

🤖 Generated with Claude Code

https://claude.ai/code/session_0122Fnwtz6X3prPd24i9hNeT

---

Generated by Claude Code

Summary by CodeRabbit

• Chores
  • Updated the project’s funding information to include cpp-linter as an Open Collective recipient. This change affects project funding details only; it does not change the application’s features or behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository UI (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 1a190645-56df-4edb-82fd-b9c5ae4303b6

📥 Commits

Reviewing files that changed from the base of the PR and between 13f9f8f and 3135811.

📒 Files selected for processing (1)

• .github/FUNDING.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The funding configuration now lists cpp-linter as an Open Collective funding recipient.

Changes

Funding Recipient Configuration

Layer / File(s)	Summary
Add Open Collective recipient .github/FUNDING.yml	The funding configuration adds cpp-linter as an Open Collective recipient.

Priority: ⬇️ Low

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

Merge Risk: ⚪ Minimal · up to 31358

The funding file lists cpp-linter as an Open Collective recipient. No actionable merge risk is identified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: adding a repository-level .github/FUNDING.yml file.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

• Autopilot · 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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[2bndy5]

Why was this closed?