Skip to content

Add funding + issue templates and pin the Gradle wrapper checksum - #22

Merged
jamesarich merged 1 commit into
mainfrom
chore/community-health-and-hardening
Jul 22, 2026
Merged

Add funding + issue templates and pin the Gradle wrapper checksum#22
jamesarich merged 1 commit into
mainfrom
chore/community-health-and-hardening

Conversation

@jamesarich

Copy link
Copy Markdown
Collaborator

Fills the remaining community-health gaps (kzstd already ships SECURITY.md, CODE_OF_CONDUCT.md, CODEOWNERS, .editorconfig): FUNDING.yml + bug/feature issue templates. Also pins distributionSha256Sum on the Gradle wrapper (9.5.1-bin, from Gradle's published checksum). No library or functional changes.

Fill remaining community-health gaps (kzstd already has SECURITY.md, CODE_OF_CONDUCT.md, CODEOWNERS, .editorconfig): FUNDING.yml + issue templates (bug/feature forms). Also pin distributionSha256Sum on the Gradle wrapper (9.5.1-bin) so a tampered wrapper download is rejected. No library/functional changes.

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
@jamesarich
jamesarich enabled auto-merge July 22, 2026 11:11
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jamesarich, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 26841469-97a0-4ab7-ad71-97026dd4b79c

📥 Commits

Reviewing files that changed from the base of the PR and between 5ea22ab and 12d1832.

📒 Files selected for processing (5)
  • .github/FUNDING.yml
  • .github/ISSUE_TEMPLATE/bug_report.yml
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/ISSUE_TEMPLATE/feature_request.yml
  • gradle/wrapper/gradle-wrapper.properties

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.

@jamesarich
jamesarich disabled auto-merge July 22, 2026 11:38
@jamesarich
jamesarich merged commit b3c13ce into main Jul 22, 2026
4 checks passed
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