Skip to content

docs: update compliance status and add bash 4+ requirement #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
don-petry merged 2 commits into from
Apr 6, 2026
Merged

docs: update compliance status and add bash 4+ requirement #73

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c0b6936
docs: update compliance status and add bash 4+ requirement
Apr 6, 2026
bd8155b
fix: add bash 4+ runtime check to apply-repo-settings.sh
Apr 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions scripts/apply-repo-settings.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,18 @@
# DRY_RUN=true GH_TOKEN=<admin-token> ./scripts/apply-repo-settings.sh <repo-name>
#
# Requirements:
# - Bash 4+ (uses associative arrays — macOS ships Bash 3.2; use GitHub Actions or brew install bash)
# - GH_TOKEN must have admin:repo scope (or be an admin of the org)
# - gh CLI must be installed
Comment thread
don-petry marked this conversation as resolved.

set -euo pipefail

if [ "${BASH_VERSINFO[0]}" -lt 4 ]; then
echo "[ERROR] Bash 4+ required (associative arrays). Found: $BASH_VERSION" >&2
echo " On macOS: brew install bash, then run with /opt/homebrew/bin/bash" >&2
exit 1
fi

ORG="petry-projects"
DRY_RUN="${DRY_RUN:-false}"

Expand Down
33 changes: 19 additions & 14 deletions standards/github-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,20 +243,25 @@ When creating a new repository in `petry-projects`:

## Current Compliance Status

Settings deviations from the standard documented above:

| Repository | Deviations |
|------------|-----------|
| **bmad-bgreat-suite** | No rulesets, `delete_branch_on_merge: false`, `allow_auto_merge: false`, `has_wiki: true`, `has_discussions: false` |
| **ContentTwin** | `allow_auto_merge: false`, `has_discussions: false` |
| **google-app-scripts** | `allow_merge_commit: false`, `allow_rebase_merge: false` (stricter than standard), `has_discussions: false` |
| **broodly** | `has_wiki: true`, `has_discussions: false` |
| **markets** | `has_wiki: true`, `has_discussions: false` |
| **TalkTerm** | `has_wiki: true`, `has_discussions: false` |

> **Migration note:** All repos currently use classic branch protection. These
> should be migrated to rulesets per the standard above. Classic rules should
> be removed after rulesets are verified.
**Repository settings:** All 7 repos are fully compliant as of 2026-04-05
(remediated via `scripts/apply-repo-settings.sh --all`).

**Ruleset status:**

| Repository | `pr-quality` | `code-quality` | Notes |
|------------|:---:|:---:|-------|
| **.github** | — | — | No rulesets yet |
| **bmad-bgreat-suite** | — | — | No rulesets yet |
| **ContentTwin** | ✅ | — | |
| **broodly** | ✅ | — | |
| **TalkTerm** | ✅ | — | |
| **markets** | ✅ | — | |
| **google-app-scripts** | — | — | Has non-standard `protect-branches` ruleset — migrate to `pr-quality` |

> **Next steps:** Run `scripts/apply-rulesets.sh --all` to create `code-quality`
> rulesets across all repos. The `pr-quality` ruleset support needs to be added
> to `apply-rulesets.sh` (currently only handles `code-quality`).
> Migrate `google-app-scripts` from its legacy `protect-branches` ruleset.

---

Expand Down
Loading