Disable unused GitHub features & add FUNDING.yml

[nathanialhenniges]

Summary

• Disable Wiki (was enabled, unused)
• Disable Projects (was enabled, unused)
• Discussions already disabled
• Add FUNDING.yml with GitHub Sponsors config (nathanialhenniges)

Acceptance Criteria

• Wiki disabled
• Projects disabled
• Discussions disabled
• FUNDING.yml added with GitHub Sponsors config

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Added a GitHub funding configuration to declare the repository’s sponsorship account for GitHub Sponsors, enabling display of the project’s designated sponsor link in supported UIs.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6c534dd0-681c-44e1-9ba4-5bef67c436cd

📥 Commits

Reviewing files that changed from the base of the PR and between d9627ee and dd65c80.

📒 Files selected for processing (1)

• .github/FUNDING.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/FUNDING.yml

---

Walkthrough

A new GitHub funding configuration file .github/FUNDING.yml is added that declares only the repository's GitHub sponsor account using the provided username; no other platforms, runtime logic, or code changes are included.

Changes

Cohort / File(s)	Summary
GitHub Funding Configuration .github/FUNDING.yml	Adds a single-entry funding file declaring the repository's github sponsor username; no other platforms or runtime changes included.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 I found a file and gave a cheer,
A tiny tag to show who's near.
One name for GitHub, neat and spry,
A rabbit's hop — a sponsor's hi! 🥕

🚥 Pre-merge checks | ✅ 3

✅ 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 partially relates to the changeset by mentioning FUNDING.yml addition, but does not clearly represent the main change since the PR also involves disabling GitHub features. The title is somewhat broad and uses an ampersand separator.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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 chore/disable-unused-features-add-funding

---

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

[coderabbitai]

🧹 Nitpick comments (1)

.github/FUNDING.yml (1)

4-13: Remove unused template boilerplate.

Lines 4–13 are all empty placeholder entries carried over from a template. The FUNDING.yml file lives in the repository's .github folder as a static config — including empty keys just adds noise with no functional effect. Since the PR's stated intent is only to configure GitHub Sponsors, every entry without a value can be dropped.

♻️ Proposed cleanup

 # These are supported funding model platforms

 github: nathanialhenniges # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
-patreon: # Replace with a single Patreon username
-open_collective: # Replace with a single Open Collective username
-ko_fi: # Replace with a single Ko-fi username
-tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
-liberapay: # Replace with a single Liberapay username
-issuehunt: # Replace with a single IssueHunt username
-otechie: # Replace with a single Otechie username
-lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
-custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/FUNDING.yml around lines 4 - 13, Remove the unused empty template
keys from .github/FUNDING.yml — delete the placeholder entries patreon,
open_collective, ko_fi, tidelift, community_bridge, liberapay, issuehunt,
otechie, lfx_crowdfunding and custom so only the intended GitHub Sponsors
configuration remains; ensure the file contains only the actual sponsor key(s)
you want configured (e.g., sponsors) and no empty or commented template lines.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/FUNDING.yml:
- Around line 4-13: Remove the unused empty template keys from
.github/FUNDING.yml — delete the placeholder entries patreon, open_collective,
ko_fi, tidelift, community_bridge, liberapay, issuehunt, otechie,
lfx_crowdfunding and custom so only the intended GitHub Sponsors configuration
remains; ensure the file contains only the actual sponsor key(s) you want
configured (e.g., sponsors) and no empty or commented template lines.