chore: add PR title check and funding config

[teneplaysofficial]

Summary by CodeRabbit

• Chores
  • Added GitHub funding configuration.
  • Added pull request title validation automation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two GitHub configuration files added: a funding specification file identifying the GitHub organization handle and a GitHub Actions workflow automating PR title validation using the Sheriff action on pull requests.

Changes

Cohort / File(s)	Summary
GitHub Configuration ​.github/FUNDING.yml, ​.github/workflows/check-pr-title.yml	Added funding metadata pointing to GitHub organization teneplaysofficial. Introduced new GitHub Actions workflow "Sheriff" triggered on PR open/edit events to validate PR titles using the teneplaysofficial/sheriff@v4 action.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A rabbit hops through GitHub's halls,
Adding funding signs and workflow calls,
The Sheriff now watches each PR's name,
With checks and balances in the game! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title mentions both PR title check and funding config, covering the main changes in the changeset (.github/workflows/check-pr-title.yml and .github/FUNDING.yml).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci

Warning

Tools execution failed with the following error:

Failed to run tools: Ping-pong health check failed

---

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

[gemini-code-assist]

Summary of Changes

Hello @teneplaysofficial, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a FUNDING.yml file to the repository, enabling the configuration of GitHub Sponsors. This allows contributors and users to financially support the project through GitHub's sponsorship program. It's worth noting that the pull request title indicates a change related to a CI workflow for PR title checks, which is not reflected in the actual file changes.

Highlights

• GitHub Sponsors Configuration: A new .github/FUNDING.yml file has been added to configure GitHub Sponsors for the repository, allowing users to support the project financially.
• PR Title Mismatch: The pull request title 'ci: add PR title check workflow' does not align with the actual changes, which involve adding a FUNDING.yml file, not a CI workflow.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/check-pr-title.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a .github/FUNDING.yml file to configure GitHub Sponsors. While the file itself is valid, the pull request title, ci: add PR title check workflow, is inaccurate and does not describe the actual changes. To ensure the project's commit history is clear and maintainable, it's important that PR titles accurately reflect their contents. I recommend updating the title to something more descriptive, like chore: Add FUNDING.yml.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eb24f3e and 40d43dc.

📒 Files selected for processing (2)

• .github/FUNDING.yml
• .github/workflows/check-pr-title.yml

🔇 Additional comments (3)

.github/FUNDING.yml (1)

1-1: LGTM!

The funding configuration is correctly formatted and follows GitHub's standard FUNDING.yml syntax.

.github/workflows/check-pr-title.yml (2)

7-8: Unable to verify Sheriff action permission requirements - external documentation inaccessible.

The referenced Sheriff action at teneplaysofficial/sheriff could not be located through public sources or repository access. Without access to the action's documentation or the actual workflow file, the claim about insufficient read-only permissions cannot be verified. Confirm whether:

• The action exists and is publicly available
• The exact name and source of the action being used
• Any error logs or behavior indicating insufficient permissions

---

14-14: Action cannot be verified in public sources; unable to confirm specific requirements.

The teneplaysofficial/sheriff@v4 action could not be found in public GitHub repositories or the GitHub Actions Marketplace. Without access to the action's action.yml documentation, it's not possible to verify:

• Whether GITHUB_TOKEN is a required or optional input
• What permissions the action actually needs
• The commit SHA for the v4 release

If this is a private action, please provide the repository link or action documentation so token requirements can be confirmed. If the action name is incorrect, verify the correct namespace and action name before implementing changes.