feat: Add ruleset JSON files to .github/rulesets/

Open Beginner friendly
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
github
Domain
devops

Research direction

Start by reviewing the listed .github/rulesets/*.json paths and the source gist installation command in the issue. Compare the four ruleset definitions with the files from templates.hbs(github/rulesets), then verify that all four JSON files are present, valid, and match the intended version-controlled ruleset definitions.

Written by the indexing model from the issue text.

Description

Description

Add GitHub ruleset JSON files from templates.hbs(github/rulesets) gist to enable version-controlled ruleset definitions.

Files

  • .github/rulesets/main-branch-protection.json
  • .github/rulesets/main-pr-reviews.json
  • .github/rulesets/integration-branch-protection.json
  • .github/rulesets/integration-pr-reviews.json

Source

Installed via:

gh gist clone ddb7525aa0b31d30415cbce2eb36bf59 gist-github-rulesets
INSTALL_DIR=. just --justfile gist-github-rulesets/github_rulesets.just install
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aRustyDev/tmpl-precommit-hook

All issues in aRustyDev/tmpl-precommit-hook

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.