Skip to content

Unsupported settings

Not all features or settings of a GitHub organization and its associated resources can be managed by the means of otterdog. The following non-exhaustive list outlines settings that are currently not supported:

  • setting the profile picture of an organization or a social media preview for a repository #119
  • manage release entries, packages, or deployments that should be visible on the main page
  • manage default repository labels on organization level
  • secrets and variables for Copilot agents
  • managing GitHub apps or oauth policies
  • managing pinned repositories for an organization
  • managing individual collaborators of repositories, use teams and team_permissions instead
  • supporting merge queue settings for a branch protection rule #86, use the required_merge_queue setting of a ruleset instead
  • ruleset rules and parameters other than those listed in Rulesets or branch protection rules, e.g. the required reviewers of the rule requiring a pull request
  • targeting the repositories of an organization ruleset by custom properties
  • deploy keys as bypass actors of a ruleset
  • requiring actions to be pinned to a full-length commit SHA in the GitHub Actions settings
  • transfer a repo from one organization to another organization
  • (deprecated) tag protections #143, use rulesets instead, see Protecting tags and releases

Most of the unsupported settings are only accessible via the Web UI of GitHub. In case you would like to have a specific feature of GitHub being supported by otterdog, please open a ticket.