You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added support for templates in required-file blueprints. (#322)
Added support for a post-add-objects hook in the default configuration that gets executed after resources have been added. (#318)
Added new blueprint pin_workflow to pin used GitHub actions in workflows.
Added new blueprint required_file to create files in repositories.
Added a new operation list-advisories to list GitHub Security Advisories for organizations.
Changed
Added raising an InsufficientPermissionsException if the token lacks required OAuth scopes for a specific endpoint. (#126)
Improved the check mechanism for blueprints by only checking a certain number each run and by taking the last check time into account.
Improved the update mechanism when installing a new GitHub organization to only update the newly added organization. (#349)
Integrated existing logging with standard python logging facility.
Utilized rich console formatting instead of low-level colorama styles.
Improved processing when archiving repositories to process all other requested changes before archiving them. (#134)
Split up policies into policies and blueprint and added support for them in the UI
Improved processing of organization settings web_commit_signoff_required and actions_can_approve_pull_request_reviews to force update the same settings on repo level as changes will be implicitly performed by GitHub.
Fixed
Fixed retrieval of setting two_factor_requirement which has been renamed to two_factor_required in the Web UI. (#339)
Fixed exclusion of settings that can only be accessed via the Web UI in the local-apply operation. (#330)
Fixed updating or deleting webhooks with wildcard patterns via the local-apply operation. (#325)
Fixed importing of rulesets due to missing handling of embedded model object required_status_checks.
Changing setting squash_merge_commit_message also requires that setting squash_merge_commit_title is present in the payload sent to GitHub.