feat: enable daily safe-settings sync and clean up documentation - #216
Merged
marcusburghardt merged 2 commits intoSep 4, 2026
Merged
Conversation
marcusburghardt
requested review from
gxmiranda,
jflowers and
jpower432
as code owners
September 4, 2026 11:30
Add a daily schedule trigger at 07:00 UTC, after peribolos apply (05:30 UTC, ~40 min runtime) to ensure org membership is current before safe-settings applies repository settings. Scheduled runs apply changes (dry-run=false) against all managed repos. Manual dispatch retains dry-run=true as default for safety. Assisted-by: OpenCode (claude-opus-4-6) Signed-off-by: Marcus Burghardt <maburgha@redhat.com>
Remove migration-era comments from safe-settings config files: - settings.yml: remove future-tense comments, gemara reference - repos/complyctl.yml: remove manual ruleset ID reference - repos/complytime.yml: remove manual ruleset ID reference - suborgs/code-repos.yml: remove gemara reference - suborgs/non-code-repos.yml: fix inaccurate description Update MAINTAINING.md to reflect current state: - Replace "Future automation" with "Automation" (schedule is live) - Update troubleshooting to reference daily sync instead of manual-only - Add deployment-settings.yml step to new repo workflow - Remove gemara-content-service from excluded repos - Fix restrictedRepos description (include-based, not exclude) - Remove completed Migration Notes section Assisted-by: OpenCode (claude-opus-4-6) Signed-off-by: Marcus Burghardt <maburgha@redhat.com>
marcusburghardt
force-pushed
the
chore/enable-safe-settings-schedule
branch
from
September 4, 2026 14:52
f7009b8 to
fc9e4f4
Compare
Member
Author
|
@gxmiranda I had to rebase in order to resolve the conflict. |
marcusburghardt
enabled auto-merge (rebase)
September 4, 2026 14:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enable the Safe Settings Sync workflow to run daily and clean up all
outdated migration-era comments and documentation.
Changes
Commit 1: Enable daily schedule
scheduletrigger at 07:00 UTC (90-minute window afterperibolos apply at 05:30 UTC, which can take ~40 minutes)
dry-run=false)dry-run=trueas default for safetyinfofor scheduled runs (notdebug)Commit 2: Clean up outdated comments and documentation
safe-settings config files:
org-wide", "Currently only on") that described planned changes
which are now the current state
gemara-content-servicereferences (no longer in the org)code owner review)
MAINTAINING.md:
is now live)
deployment-settings.ymlstep to "Add a New Repository" workflowrestrictedReposdescription (include-based allowlist, notexclude)