Skip to content

ask sponsor#385

Merged
suzuki-shunsuke merged 1 commit into
mainfrom
ask-sponsor
Jun 12, 2026
Merged

ask sponsor#385
suzuki-shunsuke merged 1 commit into
mainfrom
ask-sponsor

Conversation

@suzuki-shunsuke

@suzuki-shunsuke suzuki-shunsuke commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

Release Notes

  • Chores
    • Added GitHub Actions workflows to automate pull request processing.
    • New workflow checks GitHub Sponsor status of pull request authors and posts notifications or sponsor-request messages on pull requests.

@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

Adds a new GitHub Actions workflow system comprising a trigger workflow and a reusable workflow that automatically checks pull request authors against GitHub Sponsor databases and either confirms sponsorship or posts a sponsorship request comment to the pull request.

Changes

GitHub Sponsor Check Workflow

Layer / File(s) Summary
Pull request trigger workflow
.github/workflows/ask_sponsor.yaml
The ask_sponsor workflow fires on newly opened pull requests from user-type authors and invokes the reusable sponsor check workflow, passing author login and PR number.
Reusable workflow interface and configuration
.github/workflows/wc_ask_sponsor.yaml
The wc_ask_sponsor workflow defines inputs for author and pr_number, configures the job runner and timeout, sets up environment variables with the GitHub token, and prepares the multi-line sponsor request comment body.
Sponsor verification and feedback logic
.github/workflows/wc_ask_sponsor.yaml
The workflow queries GitHub Sponsor API to check if the author sponsors aquaproj, then suzuki-shunsuke, emitting a notice on match; if neither check succeeds, it posts a PR comment requesting the author to become a public sponsor.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes


🐰 A workflow born to check who gives back,
Two sponsor accounts, no lack-of-tack,
If sponsorship's found, we celebrate grand,
If not, a kind note, help out our brand! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The pull request title 'ask sponsor' is vague and generic, lacking specificity about what is being added or changed. Provide a more descriptive title that specifies the change, such as 'Add GitHub Actions workflow to request sponsorship' or 'Add ask_sponsor workflow to prompt PR authors for sponsorship'.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ask-sponsor

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 and usage tips.

@suzuki-shunsuke suzuki-shunsuke merged commit 3b036e6 into main Jun 12, 2026
3 of 4 checks passed
@suzuki-shunsuke suzuki-shunsuke deleted the ask-sponsor branch June 12, 2026 08:44
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