chore: add a repo-level FUNDING.yml

[shenxianpeng]

Requested by Xianpeng · project thread

Summary

Before: ecosyste.ms lists cpp-linter-action with empty funding_links. The repo has no FUNDING.yml of its own and relies on the org-level one in cpp-linter/.github, which ecosyste.ms apparently does not read. Dependency-based funds that pay through ecosyste.ms data therefore don't know where to send money.

After: .github/FUNDING.yml in this repo lists the Open Collective, so ecosyste.ms Funds (whose FAQ says it pays through each repo's FUNDING.yml) can find it on its next crawl. 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

None.

🤖 Generated with Claude Code

https://claude.ai/code/session_0122Fnwtz6X3prPd24i9hNeT

---

Generated by Claude Code

Summary by CodeRabbit

• New Features
  • Added an Open Collective funding option for the project. Supporters can now use Open Collective to contribute financially, alongside any other funding options already available. This change applies to project funding information and does not alter the app’s functionality.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 228e0adc-2a4a-45ff-8760-0eba8bfbbdb2

📥 Commits

Reviewing files that changed from the base of the PR and between 9306e59 and 0b5382e.

📒 Files selected for processing (1)

• .github/FUNDING.yml

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

---

Walkthrough

The funding configuration adds an Open Collective entry with the value cpp-linter.

Changes

Funding configuration

Layer / File(s)	Summary
Add Open Collective entry .github/FUNDING.yml	The funding configuration sets open_collective to cpp-linter.

Priority: ⬇️ Low

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

Merge Risk: ⚪ Minimal · up to 0b538

The funding entry links to the intended cpp-linter Collective. No material merge risk remains; the change is ready for normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: adding a repository-level .github/FUNDING.yml file.
Docstring Coverage	✅ Passed	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	✅ 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.

• 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.}

[shenxianpeng]

Enable auto-merge. Let's see if we can get something

[2bndy5]

I was curious about auto-merge feature. There's a premium feature called merge queue that looks great for separating large PRs into smaller PRs...