GitHub Settings as Code

Version updated for https://github.com/Vivswan/github-settings-as-code to version v2.1.0.

  • This action is used across all versions by 15 repositories.

Action Type

This is a Node action using Node version 24.

Go to the GitHub Marketplace to find the latest changes.

Action Summary

This GitHub Action automates the application of declarative repository settings from a .github/settings.yml file using a fine-grained personal access token. It replaces the Probot Settings app and manages rulesets such as branch protection and push policies. The action provides visible, stateless workflow runs that report errors if apply fails. It also includes a JSON Schema for the configuration, which is generated from Zod schemas in src/schema.ts.

What’s Changed

2.1.0 (2026-08-12)

Features

  • attest build provenance and attach the sigstore bundle to releases (d12eeb8)

Bug Fixes

  • apply review fixes to the docs and tooling sweep (a849b19)
  • apply review fixes to the harness audit batch (01e9e3b)
  • apply review fixes to the src-side audit batch (ed29870)
  • centralize the token-leak sweep in the runner (84f5ae1)
  • classify rate limits structurally on every path (0c2eb3c)
  • correct mock identity minting and the pages resurrect bug (5650244)
  • cover every faultable section in the fuzz fault battery (f683bb3)
  • derive owner-kind sensitivity from the section declaration (5d2b67e)
  • discover schema-corpus scenarios across all scenario roots (4171f1b)
  • harden the CI tooling (2c1b360)
  • keep spec-pinned gaps out of automatic graduation (ae278c9)
  • reject required-sections entries excluded by the sections allowlist (13b59f5)
  • size the harness kill cap for the directed fuzz battery (8543af8)
  • strengthen the remaining per-section representations (9567f3f)