Skip to content

chore: add a repo-level FUNDING.yml - #297

Closed
shenxianpeng wants to merge 1 commit into
mainfrom
claude/project-thread-3qatfq
Closed

shenxianpeng wants to merge 1 commit into
mainfrom
claude/project-thread-3qatfq

Conversation

@shenxianpeng

@shenxianpeng shenxianpeng commented Oct 8, 2026 •

Copy link
Copy Markdown
Member

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 list cpp-linter as its Open Collective recipient. This change affects how the project’s funding destination is identified; it does not change application functionality.

List the Open Collective so dependency-based funds that read each
repository's own FUNDING.yml (such as ecosyste.ms Funds) know where to
send money. GitHub Sponsors is left out until the org profile is live.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0122Fnwtz6X3prPd24i9hNeT
@sonarqubecloud

sonarqubecloud Bot commented Oct 8, 2026

Copy link
Copy Markdown

@shenxianpeng shenxianpeng self-assigned this Oct 8, 2026
@codecov

codecov Bot commented Oct 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (b1c0fc8) to head (20aa07f).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #297   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines          248       248           
=========================================
  Hits           248       248           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@coderabbitai

coderabbitai Bot commented Oct 8, 2026

Copy link
Copy Markdown

Review in Change Stack →

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: 9047d2ba-3564-408a-929d-0ef057d6671a
📥 Commits

Reviewing files that changed from the base of the PR and between b1c0fc8 and 20aa07f.

📒 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

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

Changes

Funding configuration

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

Priority: ⬇️ Low

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

Merge Risk: ⚪ Minimal · up to 20aa0

The repository-level funding entry points to the project’s documented Open Collective destination; no merge-blocking risk is evident.

🚥 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 and concisely 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

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

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