Règles - Documentation GitHub

Get all organization repository rulesets

Compatible avec GitHub Apps

Get all the repository rulesets for an organization.

Paramètres pour « Get all organization repository rulesets »

En-têtes
Nom, Type, Description
`accept` string Setting to `application/vnd.github+json` is recommended.
Paramètres de chemin d’accès
Nom, Type, Description
`org` string Obligatoire The organization name. The name is not case sensitive.

Codes d’état de la réponse HTTP pour « Get all organization repository rulesets »

Code d’état	Description
`200`	OK
`404`	Resource not found
`500`	Internal Error

Exemples de code pour « Get all organization repository rulesets »

get/orgs/{org}/rulesets

curl -L \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR-TOKEN>"\
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/orgs/ORG/rulesets

Response

Status: 200

[
  {
    "id": 21,
    "name": "super cool ruleset",
    "source_type": "Organization",
    "source": "my-org",
    "enforcement": "enabled"
  },
  {
    "id": 432,
    "name": "Another ruleset",
    "source_type": "Organization",
    "source": "my-org",
    "enforcement": "enabled"
  }
]

Create an organization repository ruleset

Compatible avec GitHub Apps

Create a repository ruleset for an organization.

Paramètres pour « Create an organization repository ruleset »

En-têtes

Nom, Type, Description

accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès

Nom, Type, Description

org string Obligatoire

The organization name. The name is not case sensitive.

Paramètres du corps

Nom, Type, Description

name string Obligatoire

The name of the ruleset.

target string

The target of the ruleset.

Peut être: branch, tag

enforcement string Obligatoire

The enforcement level of the ruleset. evaluate allows admins to test rules before enforcing them. Admins can view insights on the Rule Insights page (evaluate is only available with GitHub Enterprise).

Peut être: disabled, active, evaluate

bypass_actors array of objects

The actors that can bypass the rules in this ruleset

Properties of bypass_actors

Nom, Type, Description
`actor_id` integer The ID of the actor that can bypass a ruleset
`actor_type` string The type of actor that can bypass a ruleset Peut être: `Team`, `Integration`

conditions object

Conditions for a organization ruleset

rules array of objects

An array of rules within the ruleset.

Can be one of these objects:

Nom, Type, Description

creation object Obligatoire

Parameters to be used for the creation rule

Properties of creation

Nom, Type, Description
`type` string Obligatoire Value: `creation`

update object Obligatoire

Parameters to be used for the update rule

Properties of update

Nom, Type, Description

type string Obligatoire

Value: update

parameters object

Properties of parameters

Nom, Type, Description
`update_allows_fetch_and_merge` boolean Obligatoire Branch can pull changes from its upstream repository

deletion object Obligatoire

Parameters to be used for the deletion rule

Properties of deletion

Nom, Type, Description
`type` string Obligatoire Value: `deletion`

required_linear_history object Obligatoire

Parameters to be used for the required_linear_history rule

Properties of required_linear_history

Nom, Type, Description
`type` string Obligatoire Value: `required_linear_history`

required_deployments object Obligatoire

Parameters to be used for the required_deployments rule

Properties of required_deployments

Nom, Type, Description

type string Obligatoire

Value: required_deployments

parameters object

Properties of parameters

Nom, Type, Description
`required_deployment_environments` array of strings Obligatoire The environments that must be successfully deployed to before branches can be merged.

required_signatures object Obligatoire

Parameters to be used for the required_signatures rule

Properties of required_signatures

Nom, Type, Description
`type` string Obligatoire Value: `required_signatures`

pull_request object Obligatoire

Parameters to be used for the pull_request rule

Properties of pull_request

Nom, Type, Description

type string Obligatoire

Value: pull_request

parameters object

Properties of parameters

Nom, Type, Description
`dismiss_stale_reviews_on_push` boolean Obligatoire New, reviewable commits pushed will dismiss previous pull request review approvals.
`require_code_owner_review` boolean Obligatoire Require an approving review in pull requests that modify files that have a designated code owner.
`require_last_push_approval` boolean Obligatoire Whether the most recent reviewable push must be approved by someone other than the person who pushed it.
`required_approving_review_count` integer Obligatoire The number of approving reviews that are required before a pull request can be merged.
`required_review_thread_resolution` boolean Obligatoire All conversations on code must be resolved before a pull request can be merged.

required_status_checks object Obligatoire

Parameters to be used for the required_status_checks rule

Properties of required_status_checks

Nom, Type, Description

type string Obligatoire

Value: required_status_checks

parameters object

Properties of parameters

Nom, Type, Description

required_status_checks array of objects Obligatoire

Status checks that are required.

Properties of required_status_checks

Nom, Type, Description
`context` string Obligatoire The status check context name that must be present on the commit.
`integration_id` integer The optional integration ID that this status check must originate from.

strict_required_status_checks_policy boolean Obligatoire

Whether pull requests targeting a matching branch must be tested with the latest code. This setting will not take effect unless at least one status check is enabled.

non_fast_forward object Obligatoire

Parameters to be used for the non_fast_forward rule

Properties of non_fast_forward

Nom, Type, Description
`type` string Obligatoire Value: `non_fast_forward`

commit_message_pattern object Obligatoire

Parameters to be used for the commit_message_pattern rule

Properties of commit_message_pattern

Nom, Type, Description

type string Obligatoire

Value: commit_message_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

commit_author_email_pattern object Obligatoire

Parameters to be used for the commit_author_email_pattern rule

Properties of commit_author_email_pattern

Nom, Type, Description

type string Obligatoire

Value: commit_author_email_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

committer_email_pattern object Obligatoire

Parameters to be used for the committer_email_pattern rule

Properties of committer_email_pattern

Nom, Type, Description

type string Obligatoire

Value: committer_email_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

branch_name_pattern object Obligatoire

Parameters to be used for the branch_name_pattern rule

Properties of branch_name_pattern

Nom, Type, Description

type string Obligatoire

Value: branch_name_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

tag_name_pattern object Obligatoire

Parameters to be used for the tag_name_pattern rule

Properties of tag_name_pattern

Nom, Type, Description

type string Obligatoire

Value: tag_name_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

Codes d’état de la réponse HTTP pour « Create an organization repository ruleset »

Code d’état	Description
`201`	Created
`404`	Resource not found
`500`	Internal Error

Exemples de code pour « Create an organization repository ruleset »

post/orgs/{org}/rulesets

curl -L \
  -X POST \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR-TOKEN>"\
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/orgs/ORG/rulesets \
  -d '{"name":"super cool ruleset","target":"branch","enforcement":"active","bypass_actors":[{"actor_id":234,"actor_type":"Team"}],"conditions":{"ref_name":{"include":["refs/heads/main","refs/heads/master"],"exclude":["refs/heads/dev*"]}},"rules":[{"type":"commit_author_email_pattern","parameters":{"operator":"contains","pattern":"github"}}]}'

Response

Status: 201

{
  "id": 21,
  "name": "super cool ruleset",
  "target": "branch",
  "source_type": "Organization",
  "source": "my-org",
  "enforcement": "active",
  "bypass_actors": [
    {
      "actor_id": 234,
      "actor_type": "Team"
    }
  ],
  "conditions": {
    "ref_name": {
      "include": [
        "refs/heads/main",
        "refs/heads/master"
      ],
      "exclude": [
        "refs/heads/dev*"
      ]
    },
    "repository_name": {
      "include": [
        "important_repository",
        "another_important_repository"
      ],
      "exclude": [
        "unimportant_repository"
      ],
      "protected": true
    }
  },
  "rules": [
    {
      "type": "commit_author_email_pattern",
      "parameters": {
        "operator": "contains",
        "pattern": "github"
      }
    }
  ]
}

Get an organization repository ruleset

Compatible avec GitHub Apps

Get a repository ruleset for an organization.

Paramètres pour « Get an organization repository ruleset »

En-têtes
Nom, Type, Description
`accept` string Setting to `application/vnd.github+json` is recommended.
Paramètres de chemin d’accès
Nom, Type, Description
`org` string Obligatoire The organization name. The name is not case sensitive.
`ruleset_id` integer Obligatoire The ID of the ruleset.

Codes d’état de la réponse HTTP pour « Get an organization repository ruleset »

Code d’état	Description
`200`	OK
`404`	Resource not found
`500`	Internal Error

Exemples de code pour « Get an organization repository ruleset »

get/orgs/{org}/rulesets/{ruleset_id}

curl -L \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR-TOKEN>"\
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/orgs/ORG/rulesets/RULESET_ID

Response

Status: 200

{
  "id": 21,
  "name": "super cool ruleset",
  "target": "branch",
  "source_type": "Organization",
  "source": "my-org",
  "enforcement": "active",
  "bypass_actors": [
    {
      "actor_id": 234,
      "actor_type": "Team"
    }
  ],
  "conditions": {
    "ref_name": {
      "include": [
        "refs/heads/main",
        "refs/heads/master"
      ],
      "exclude": [
        "refs/heads/dev*"
      ]
    },
    "repository_name": {
      "include": [
        "important_repository",
        "another_important_repository"
      ],
      "exclude": [
        "unimportant_repository"
      ],
      "protected": true
    }
  },
  "rules": [
    {
      "type": "commit_author_email_pattern",
      "parameters": {
        "operator": "contains",
        "pattern": "github"
      }
    }
  ]
}

Update an organization repository ruleset

Compatible avec GitHub Apps

Update a ruleset for an organization.

Paramètres pour « Update an organization repository ruleset »

En-têtes

Nom, Type, Description

accept string

Setting to application/vnd.github+json is recommended.

Paramètres de chemin d’accès

Nom, Type, Description

org string Obligatoire

The organization name. The name is not case sensitive.

ruleset_id integer Obligatoire

The ID of the ruleset.

Paramètres du corps

Nom, Type, Description

name string

The name of the ruleset.

target string

The target of the ruleset.

Peut être: branch, tag

enforcement string

Peut être: disabled, active, evaluate

bypass_actors array of objects

The actors that can bypass the rules in this ruleset

Properties of bypass_actors

Nom, Type, Description
`actor_id` integer The ID of the actor that can bypass a ruleset
`actor_type` string The type of actor that can bypass a ruleset Peut être: `Team`, `Integration`

conditions object

Conditions for a organization ruleset

rules array of objects

An array of rules within the ruleset.

Can be one of these objects:

Nom, Type, Description

creation object Obligatoire

Parameters to be used for the creation rule

Properties of creation

Nom, Type, Description
`type` string Obligatoire Value: `creation`

update object Obligatoire

Parameters to be used for the update rule

Properties of update

Nom, Type, Description

type string Obligatoire

Value: update

parameters object

Properties of parameters

Nom, Type, Description
`update_allows_fetch_and_merge` boolean Obligatoire Branch can pull changes from its upstream repository

deletion object Obligatoire

Parameters to be used for the deletion rule

Properties of deletion

Nom, Type, Description
`type` string Obligatoire Value: `deletion`

required_linear_history object Obligatoire

Parameters to be used for the required_linear_history rule

Properties of required_linear_history

Nom, Type, Description
`type` string Obligatoire Value: `required_linear_history`

required_deployments object Obligatoire

Parameters to be used for the required_deployments rule

Properties of required_deployments

Nom, Type, Description

type string Obligatoire

Value: required_deployments

parameters object

Properties of parameters

Nom, Type, Description
`required_deployment_environments` array of strings Obligatoire The environments that must be successfully deployed to before branches can be merged.

required_signatures object Obligatoire

Parameters to be used for the required_signatures rule

Properties of required_signatures

Nom, Type, Description
`type` string Obligatoire Value: `required_signatures`

pull_request object Obligatoire

Parameters to be used for the pull_request rule

Properties of pull_request

Nom, Type, Description

type string Obligatoire

Value: pull_request

parameters object

Properties of parameters

Nom, Type, Description
`dismiss_stale_reviews_on_push` boolean Obligatoire New, reviewable commits pushed will dismiss previous pull request review approvals.
`require_code_owner_review` boolean Obligatoire Require an approving review in pull requests that modify files that have a designated code owner.
`require_last_push_approval` boolean Obligatoire Whether the most recent reviewable push must be approved by someone other than the person who pushed it.
`required_approving_review_count` integer Obligatoire The number of approving reviews that are required before a pull request can be merged.
`required_review_thread_resolution` boolean Obligatoire All conversations on code must be resolved before a pull request can be merged.

required_status_checks object Obligatoire

Parameters to be used for the required_status_checks rule

Properties of required_status_checks

Nom, Type, Description

type string Obligatoire

Value: required_status_checks

parameters object

Properties of parameters

Nom, Type, Description

required_status_checks array of objects Obligatoire

Status checks that are required.

Properties of required_status_checks

Nom, Type, Description
`context` string Obligatoire The status check context name that must be present on the commit.
`integration_id` integer The optional integration ID that this status check must originate from.

strict_required_status_checks_policy boolean Obligatoire

Whether pull requests targeting a matching branch must be tested with the latest code. This setting will not take effect unless at least one status check is enabled.

non_fast_forward object Obligatoire

Parameters to be used for the non_fast_forward rule

Properties of non_fast_forward

Nom, Type, Description
`type` string Obligatoire Value: `non_fast_forward`

commit_message_pattern object Obligatoire

Parameters to be used for the commit_message_pattern rule

Properties of commit_message_pattern

Nom, Type, Description

type string Obligatoire

Value: commit_message_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

commit_author_email_pattern object Obligatoire

Parameters to be used for the commit_author_email_pattern rule

Properties of commit_author_email_pattern

Nom, Type, Description

type string Obligatoire

Value: commit_author_email_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

committer_email_pattern object Obligatoire

Parameters to be used for the committer_email_pattern rule

Properties of committer_email_pattern

Nom, Type, Description

type string Obligatoire

Value: committer_email_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

branch_name_pattern object Obligatoire

Parameters to be used for the branch_name_pattern rule

Properties of branch_name_pattern

Nom, Type, Description

type string Obligatoire

Value: branch_name_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

tag_name_pattern object Obligatoire

Parameters to be used for the tag_name_pattern rule

Properties of tag_name_pattern

Nom, Type, Description

type string Obligatoire

Value: tag_name_pattern

parameters object

Properties of parameters

Nom, Type, Description
`name` string How this rule will appear to users.
`negate` boolean If true, the rule will fail if the pattern matches.
`operator` string Obligatoire The operator to use for matching. Peut être: `starts_with`, `ends_with`, `contains`, `regex`
`pattern` string Obligatoire The pattern to match with.

Codes d’état de la réponse HTTP pour « Update an organization repository ruleset »

Code d’état	Description
`200`	OK
`404`	Resource not found
`500`	Internal Error

Exemples de code pour « Update an organization repository ruleset »

put/orgs/{org}/rulesets/{ruleset_id}

curl -L \
  -X PUT \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR-TOKEN>"\
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/orgs/ORG/rulesets/RULESET_ID \
  -d '{"name":"super cool ruleset","target":"branch","enforcement":"active","bypass_actors":[{"actor_id":234,"actor_type":"Team"}],"conditions":{"ref_name":{"include":["refs/heads/main","refs/heads/master"],"exclude":["refs/heads/dev*"]}},"rules":[{"type":"commit_author_email_pattern","parameters":{"operator":"contains","pattern":"github"}}]}'

Response

Status: 200

{
  "id": 21,
  "name": "super cool ruleset",
  "target": "branch",
  "source_type": "Organization",
  "source": "my-org",
  "enforcement": "active",
  "bypass_actors": [
    {
      "actor_id": 234,
      "actor_type": "Team"
    }
  ],
  "conditions": {
    "ref_name": {
      "include": [
        "refs/heads/main",
        "refs/heads/master"
      ],
      "exclude": [
        "refs/heads/dev*"
      ]
    },
    "repository_name": {
      "include": [
        "important_repository",
        "another_important_repository"
      ],
      "exclude": [
        "unimportant_repository"
      ],
      "protected": true
    }
  },
  "rules": [
    {
      "type": "commit_author_email_pattern",
      "parameters": {
        "operator": "contains",
        "pattern": "github"
      }
    }
  ]
}

Delete an organization repository ruleset

Compatible avec GitHub Apps

Delete a ruleset for an organization.

Paramètres pour « Delete an organization repository ruleset »

En-têtes
Nom, Type, Description
`accept` string Setting to `application/vnd.github+json` is recommended.
Paramètres de chemin d’accès
Nom, Type, Description
`org` string Obligatoire The organization name. The name is not case sensitive.
`ruleset_id` integer Obligatoire The ID of the ruleset.

Codes d’état de la réponse HTTP pour « Delete an organization repository ruleset »

Code d’état	Description
`204`	No Content
`404`	Resource not found
`500`	Internal Error

Exemples de code pour « Delete an organization repository ruleset »

delete/orgs/{org}/rulesets/{ruleset_id}

curl -L \
  -X DELETE \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR-TOKEN>"\
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/orgs/ORG/rulesets/RULESET_ID

Response

Status: 204