Skip to content

docs: add GitHub Sponsors as a funding channel - #259

Merged
shenxianpeng merged 1 commit into
mainfrom
claude/project-thread-v087lh
Nov 12, 2026
Merged

shenxianpeng merged 1 commit into
mainfrom
claude/project-thread-v087lh

Conversation

@shenxianpeng

@shenxianpeng shenxianpeng commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

The cpp-linter GitHub Sponsors profile is now live (https://github.com/sponsors/cpp-linter). Its fiscal host is Open Source Collective, so sponsorships through GitHub land in the same Open Collective balance.

  • funding.json: add a github-sponsors channel and list it on all three plans (FLOSS/fund reads this file).
  • README Sponsors section: mention GitHub Sponsors next to Open Collective.
  • PR comment footer: the Sponsor link now points to https://cpp-linter.github.io/sponsor/, which lists both channels, so the link no longer needs a release when the channels change.

Summary by CodeRabbit

  • New Features
    • GitHub Sponsors is now available alongside Open Collective as a contribution option for supported funding plans.
  • Documentation
    • Sponsor information now links to GitHub Sponsors as well as Open Collective. The cpp-linter outreach link now points to the sponsor page.

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Nov 12, 2026
@shenxianpeng shenxianpeng self-assigned this Nov 12, 2026
@coderabbitai

coderabbitai Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The README and USER_OUTREACH now include cpp-linter sponsorship references. The funding configuration adds GitHub Sponsors as a provider and payment option for the maintenance, supply-chain-security, and cpp-linter-v2 plans.

Changes

Sponsorship updates

Layer / File(s) Summary
Sponsor links and funding plans
funding.json, README.rst, cpp_linter/rest_api.py
funding.json adds GitHub Sponsors as a provider and to three plans alongside Open Collective. The README adds a GitHub Sponsors link. USER_OUTREACH links to the cpp-linter sponsor page.

Estimated code review effort: 2 (Simple) | ~5 minutes

Merge Risk: Minimal · up to d9f95

This change adds GitHub Sponsors as a funding option and points the PR comment footer's sponsor link to the sponsor page. No merge-blocking risk was identified.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title "docs: add GitHub Sponsors as a funding channel" matches the main change. The PR adds a github-sponsors channel to funding.json on all three plans, mentions GitHub Sponsors in the README Spo…
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.
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Full details: Title check

Explanation

The title "docs: add GitHub Sponsors as a funding channel" matches the main change. The PR adds a github-sponsors channel to funding.json on all three plans, mentions GitHub Sponsors in the README Sponsors section, and points the PR comment footer's Sponsor link to the cpp-linter sponsor page. The title omits the footer link change, which is a secondary detail.

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

Share

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 9a1090c5-5747-4888-9609-7bcbb689ae17
Commits

Reviewing files that changed from the base of the PR and between cd9d31a and d9f9586.

Files selected for processing: 3

  • README.rst
  • cpp_linter/rest_api.py
  • funding.json

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

@2bndy5 2bndy5 left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think the same needs to be done in cpp-linter-rs about the USE_OUTREACH text.

Edit: now is see the PR (cpp-linter/cpp-linter-rs#571)

@shenxianpeng
shenxianpeng merged commit ca09e04 into main Nov 12, 2026
39 checks passed
@shenxianpeng
shenxianpeng deleted the claude/project-thread-v087lh branch November 12, 2026 19:56
@codecov

codecov Bot commented Nov 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (1e66706) to head (d9f9586).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #259   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           28        28           
  Lines         2451      2451           
=========================================
  Hits          2451      2451           

☔ 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.

This branch was previously deployed

1 inactive deployment
test-coverage — d9f95865 Deployed Nov 12, 2026 by shenxianpeng via coverage-report #261
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants