Points de terminaison d’API REST pour les règles
Utilisez l'API REST pour gérer les suites de règles pour les organisations. Les ensembles de règles d’organisation contrôlent la façon dont les personnes peuvent interagir avec les branches et les étiquettes sélectionnées dans les dépôts d’une organisation.
Get all organization repository rulesets
Get all the repository rulesets for an organization.
Jetons d’accès affinés pour « Get all organization repository rulesets »
Ce point de terminaison fonctionne avec les types de jetons précis suivants:
- Jetons d’accès utilisateur d’application GitHub
- Jetons d’accès d’installation d’application GitHub
- Jetons d’accès personnel affiné
Le jeton précis doit avoir l’ensemble d’autorisations suivant:
- "Administration" organization permissions (write)
Paramètres pour « Get all organization repository rulesets »
Nom, Type, Description |
---|
accept string Setting to |
Nom, Type, Description |
---|
org string ObligatoireThe organization name. The name is not case sensitive. |
Nom, Type, Description |
---|
per_page integer The number of results per page (max 100). For more information, see "Using pagination in the REST API." Default: |
page integer The page number of the results to fetch. For more information, see "Using pagination in the REST API." Default: |
targets string A comma-separated list of rule targets to filter by.
If provided, only rulesets that apply to the specified targets will be returned.
For example, |
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 »
Exemple de requête
curl -L \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2022-11-28" \
http(s)://HOSTNAME/api/v3/orgs/ORG/rulesets
Response
Status: 200
[
{
"id": 21,
"name": "super cool ruleset",
"source_type": "Organization",
"source": "my-org",
"enforcement": "enabled",
"node_id": "RRS_lACkVXNlcgQB",
"_links": {
"self": {
"href": "https://HOSTNAME/orgs/my-org/rulesets/21"
},
"html": {
"href": "https://github.com/organizations/my-org/settings/rules/21"
}
},
"created_at": "2023-07-15T08:43:03Z",
"updated_at": "2023-08-23T16:29:47Z"
},
{
"id": 432,
"name": "Another ruleset",
"source_type": "Organization",
"source": "my-org",
"enforcement": "enabled",
"node_id": "RRS_lACkVXNlcgQQ",
"_links": {
"self": {
"href": "https://HOSTNAME/orgs/my-org/rulesets/432"
},
"html": {
"href": "https://github.com/organizations/my-org/settings/rules/432"
}
},
"created_at": "2023-08-15T08:43:03Z",
"updated_at": "2023-09-23T16:29:47Z"
}
]
Create an organization repository ruleset
Create a repository ruleset for an organization.
Jetons d’accès affinés pour « Create an organization repository ruleset »
Ce point de terminaison fonctionne avec les types de jetons précis suivants:
- Jetons d’accès utilisateur d’application GitHub
- Jetons d’accès d’installation d’application GitHub
- Jetons d’accès personnel affiné
Le jeton précis doit avoir l’ensemble d’autorisations suivant:
- "Administration" organization permissions (write)
Paramètres pour « Create an organization repository ruleset »
Nom, Type, Description |
---|
accept string Setting to |
Nom, Type, Description |
---|
org string ObligatoireThe organization name. The name is not case sensitive. |
Nom, Type, Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
name string ObligatoireThe name of the ruleset. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
target string The target of the ruleset. Default: Peut être: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
enforcement string ObligatoireThe enforcement level of the ruleset. Peut être: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
bypass_actors array of objects The actors that can bypass the rules in this ruleset | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Properties of |
Nom, Type, Description |
---|
actor_id integer ObligatoireThe ID of the actor that can bypass a ruleset. If |
actor_type string ObligatoireThe type of actor that can bypass a ruleset Peut être: |
bypass_mode string ObligatoireWhen the specified actor can bypass the ruleset. Default: Peut être: |
conditions
object Conditions for an organization ruleset.
The branch and tag rulesets conditions object should contain both repository_name
and ref_name
properties, or both repository_id
and ref_name
properties, or both repository_property
and ref_name
properties.
The push rulesets conditions object does not require the ref_name
property.
Can be one of these objects:
Nom, Type, Description | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
repository_name_and_ref_name object ObligatoireConditions to target repositories by name and refs by name | |||||||||||||||||||||
Properties of |
Nom, Type, Description | ||||
---|---|---|---|---|
ref_name object | ||||
Properties of |
Nom, Type, Description |
---|
include array of strings Array of ref names or patterns to include. One of these patterns must match for the condition to pass. Also accepts |
exclude array of strings Array of ref names or patterns to exclude. The condition will not pass if any of these patterns match. |
repository_name
object ObligatoireProperties of repository_name
Nom, Type, Description |
---|
include array of strings Array of repository names or patterns to include. One of these patterns must match for the condition to pass. Also accepts |
exclude array of strings Array of repository names or patterns to exclude. The condition will not pass if any of these patterns match. |
protected boolean Whether renaming of target repositories is prevented. |
repository_id_and_ref_name
object ObligatoireConditions to target repositories by id and refs by name
Properties of repository_id_and_ref_name
Nom, Type, Description | |||
---|---|---|---|
ref_name object | |||
Properties of |
Nom, Type, Description |
---|
include array of strings Array of ref names or patterns to include. One of these patterns must match for the condition to pass. Also accepts |
exclude array of strings Array of ref names or patterns to exclude. The condition will not pass if any of these patterns match. |
repository_id
object ObligatoireProperties of repository_id
Nom, Type, Description |
---|
repository_ids array of integers The repository IDs that the ruleset applies to. One of these IDs must match for the condition to pass. |
repository_property_and_ref_name
object ObligatoireConditions to target repositories by property and refs by name
Properties of repository_property_and_ref_name
Nom, Type, Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ref_name object | |||||||||||||
Properties of |
Nom, Type, Description |
---|
include array of strings Array of ref names or patterns to include. One of these patterns must match for the condition to pass. Also accepts |
exclude array of strings Array of ref names or patterns to exclude. The condition will not pass if any of these patterns match. |
repository_property
object ObligatoireProperties of repository_property
Nom, Type, Description | ||||
---|---|---|---|---|
include array of objects The repository properties and values to include. All of these properties must match for the condition to pass. | ||||
Properties of |
Nom, Type, Description |
---|
name string ObligatoireThe name of the repository property to target |
property_values array of strings ObligatoireThe values to match for the repository property |
source string The source of the repository property. Defaults to 'custom' if not specified. Peut être: |
exclude
array of objects The repository properties and values to exclude. The condition will not pass if any of these properties match.
Properties of exclude
Nom, Type, Description |
---|
name string ObligatoireThe name of the repository property to target |
property_values array of strings ObligatoireThe values to match for the repository property |
source string The source of the repository property. Defaults to 'custom' if not specified. Peut être: |
rules
array of objects An array of rules within the ruleset.
Can be one of these objects:
Nom, Type, Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
creation object ObligatoireOnly allow users with bypass permission to create matching refs. | |||||||||||||
Properties of |
Nom, Type, Description |
---|
type string ObligatoireValue: |
update
object ObligatoireOnly allow users with bypass permission to update matching refs.
Properties of update
Nom, Type, Description | ||
---|---|---|
type string ObligatoireValue: | ||
parameters object | ||
Properties of |
Nom, Type, Description |
---|
update_allows_fetch_and_merge boolean ObligatoireBranch can pull changes from its upstream repository |
deletion
object ObligatoireOnly allow users with bypass permissions to delete matching refs.
Properties of deletion
Nom, Type, Description |
---|
type string ObligatoireValue: |
required_linear_history
object ObligatoirePrevent merge commits from being pushed to matching refs.
Properties of required_linear_history
Nom, Type, Description |
---|
type string ObligatoireValue: |
required_deployments
object ObligatoireChoose which environments must be successfully deployed to before refs can be pushed into a ref that matches this rule.
Properties of required_deployments
Nom, Type, Description | ||
---|---|---|
type string ObligatoireValue: | ||
parameters object | ||
Properties of |
Nom, Type, Description |
---|
required_deployment_environments array of strings ObligatoireThe environments that must be successfully deployed to before branches can be merged. |
required_signatures
object ObligatoireCommits pushed to matching refs must have verified signatures.
Properties of required_signatures
Nom, Type, Description |
---|
type string ObligatoireValue: |
pull_request
object ObligatoireRequire all commits be made to a non-target branch and submitted via a pull request before they can be merged.
Properties of pull_request
Nom, Type, Description | |||||||
---|---|---|---|---|---|---|---|
type string ObligatoireValue: | |||||||
parameters object | |||||||
Properties of |
Nom, Type, Description |
---|
allowed_merge_methods array of strings When merging pull requests, you can allow any combination of merge commits, squashing, or rebasing. At least one option must be enabled. |
dismiss_stale_reviews_on_push boolean ObligatoireNew, reviewable commits pushed will dismiss previous pull request review approvals. |
require_code_owner_review boolean ObligatoireRequire an approving review in pull requests that modify files that have a designated code owner. |
require_last_push_approval boolean ObligatoireWhether the most recent reviewable push must be approved by someone other than the person who pushed it. |
required_approving_review_count integer ObligatoireThe number of approving reviews that are required before a pull request can be merged. |
required_review_thread_resolution boolean ObligatoireAll conversations on code must be resolved before a pull request can be merged. |
required_status_checks
object ObligatoireChoose which status checks must pass before the ref is updated. When enabled, commits must first be pushed to another ref where the checks pass.
Properties of required_status_checks
Nom, Type, Description | ||||||||
---|---|---|---|---|---|---|---|---|
type string ObligatoireValue: | ||||||||
parameters object | ||||||||
Properties of |
Nom, Type, Description | |||
---|---|---|---|
do_not_enforce_on_create boolean Allow repositories and branches to be created if a check would otherwise prohibit it. | |||
required_status_checks array of objects ObligatoireStatus checks that are required. | |||
Properties of |
Nom, Type, Description |
---|
context string ObligatoireThe 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 ObligatoireWhether 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 ObligatoirePrevent users with push access from force pushing to refs.
Properties of non_fast_forward
Nom, Type, Description |
---|
type string ObligatoireValue: |
commit_message_pattern
object ObligatoireParameters to be used for the commit_message_pattern rule
Properties of commit_message_pattern
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
commit_author_email_pattern
object ObligatoireParameters to be used for the commit_author_email_pattern rule
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
committer_email_pattern
object ObligatoireParameters to be used for the committer_email_pattern rule
Properties of committer_email_pattern
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
branch_name_pattern
object ObligatoireParameters to be used for the branch_name_pattern rule
Properties of branch_name_pattern
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
tag_name_pattern
object ObligatoireParameters to be used for the tag_name_pattern rule
Properties of tag_name_pattern
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
workflows
object ObligatoireRequire all changes made to a targeted branch to pass the specified workflows before they can be merged.
Properties of workflows
Nom, Type, Description | |||||||||
---|---|---|---|---|---|---|---|---|---|
type string ObligatoireValue: | |||||||||
parameters object | |||||||||
Properties of |
Nom, Type, Description | |||||
---|---|---|---|---|---|
do_not_enforce_on_create boolean Allow repositories and branches to be created if a check would otherwise prohibit it. | |||||
workflows array of objects ObligatoireWorkflows that must pass for this rule to pass. | |||||
Properties of |
Nom, Type, Description |
---|
path string ObligatoireThe path to the workflow file |
ref string The ref (branch or tag) of the workflow file to use |
repository_id integer ObligatoireThe ID of the repository where the workflow is defined |
sha string The commit SHA of the workflow file to use |
source_type
string The type of the source of the ruleset
Peut être: Repository
, Organization
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 »
Exemple de requête
curl -L \
-X POST \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2022-11-28" \
http(s)://HOSTNAME/api/v3/orgs/ORG/rulesets \
-d '{"name":"super cool ruleset","target":"branch","enforcement":"active","bypass_actors":[{"actor_id":234,"actor_type":"Team","bypass_mode":"always"}],"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"}}]}'
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",
"bypass_mode": "always"
}
],
"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"
}
}
],
"node_id": "RRS_lACkVXNlcgQB",
"_links": {
"self": {
"href": "https://HOSTNAME/orgs/my-org/rulesets/21"
},
"html": {
"href": "https://github.com/organizations/my-org/settings/rules/21"
}
},
"created_at": "2023-08-15T08:43:03Z",
"updated_at": "2023-09-23T16:29:47Z"
}
Get an organization repository ruleset
Get a repository ruleset for an organization.
Note: To prevent leaking sensitive information, the bypass_actors
property is only returned if the user
making the API request has write access to the ruleset.
Jetons d’accès affinés pour « Get an organization repository ruleset »
Ce point de terminaison fonctionne avec les types de jetons précis suivants:
- Jetons d’accès utilisateur d’application GitHub
- Jetons d’accès d’installation d’application GitHub
- Jetons d’accès personnel affiné
Le jeton précis doit avoir l’ensemble d’autorisations suivant:
- "Administration" organization permissions (write)
Paramètres pour « Get an organization repository ruleset »
Nom, Type, Description |
---|
accept string Setting to |
Nom, Type, Description |
---|
org string ObligatoireThe organization name. The name is not case sensitive. |
ruleset_id integer ObligatoireThe 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 »
Exemple de requête
curl -L \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2022-11-28" \
http(s)://HOSTNAME/api/v3/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",
"bypass_mode": "always"
}
],
"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"
}
}
],
"node_id": "RRS_lACkVXNlcgQB",
"_links": {
"self": {
"href": "https://HOSTNAME/orgs/my-org/rulesets/21"
},
"html": {
"href": "https://github.com/organizations/my-org/settings/rules/21"
}
},
"created_at": "2023-08-15T08:43:03Z",
"updated_at": "2023-09-23T16:29:47Z"
}
Update an organization repository ruleset
Update a ruleset for an organization.
Jetons d’accès affinés pour « Update an organization repository ruleset »
Ce point de terminaison fonctionne avec les types de jetons précis suivants:
- Jetons d’accès utilisateur d’application GitHub
- Jetons d’accès d’installation d’application GitHub
- Jetons d’accès personnel affiné
Le jeton précis doit avoir l’ensemble d’autorisations suivant:
- "Administration" organization permissions (write)
Paramètres pour « Update an organization repository ruleset »
Nom, Type, Description |
---|
accept string Setting to |
Nom, Type, Description |
---|
org string ObligatoireThe organization name. The name is not case sensitive. |
ruleset_id integer ObligatoireThe ID of the ruleset. |
Nom, Type, Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
name string The name of the ruleset. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
target string The target of the ruleset. Peut être: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
enforcement string The enforcement level of the ruleset. Peut être: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
bypass_actors array of objects The actors that can bypass the rules in this ruleset | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Properties of |
Nom, Type, Description |
---|
actor_id integer ObligatoireThe ID of the actor that can bypass a ruleset. If |
actor_type string ObligatoireThe type of actor that can bypass a ruleset Peut être: |
bypass_mode string ObligatoireWhen the specified actor can bypass the ruleset. Default: Peut être: |
conditions
object Conditions for an organization ruleset.
The branch and tag rulesets conditions object should contain both repository_name
and ref_name
properties, or both repository_id
and ref_name
properties, or both repository_property
and ref_name
properties.
The push rulesets conditions object does not require the ref_name
property.
Can be one of these objects:
Nom, Type, Description | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
repository_name_and_ref_name object ObligatoireConditions to target repositories by name and refs by name | |||||||||||||||||||||
Properties of |
Nom, Type, Description | ||||
---|---|---|---|---|
ref_name object | ||||
Properties of |
Nom, Type, Description |
---|
include array of strings Array of ref names or patterns to include. One of these patterns must match for the condition to pass. Also accepts |
exclude array of strings Array of ref names or patterns to exclude. The condition will not pass if any of these patterns match. |
repository_name
object ObligatoireProperties of repository_name
Nom, Type, Description |
---|
include array of strings Array of repository names or patterns to include. One of these patterns must match for the condition to pass. Also accepts |
exclude array of strings Array of repository names or patterns to exclude. The condition will not pass if any of these patterns match. |
protected boolean Whether renaming of target repositories is prevented. |
repository_id_and_ref_name
object ObligatoireConditions to target repositories by id and refs by name
Properties of repository_id_and_ref_name
Nom, Type, Description | |||
---|---|---|---|
ref_name object | |||
Properties of |
Nom, Type, Description |
---|
include array of strings Array of ref names or patterns to include. One of these patterns must match for the condition to pass. Also accepts |
exclude array of strings Array of ref names or patterns to exclude. The condition will not pass if any of these patterns match. |
repository_id
object ObligatoireProperties of repository_id
Nom, Type, Description |
---|
repository_ids array of integers The repository IDs that the ruleset applies to. One of these IDs must match for the condition to pass. |
repository_property_and_ref_name
object ObligatoireConditions to target repositories by property and refs by name
Properties of repository_property_and_ref_name
Nom, Type, Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ref_name object | |||||||||||||
Properties of |
Nom, Type, Description |
---|
include array of strings Array of ref names or patterns to include. One of these patterns must match for the condition to pass. Also accepts |
exclude array of strings Array of ref names or patterns to exclude. The condition will not pass if any of these patterns match. |
repository_property
object ObligatoireProperties of repository_property
Nom, Type, Description | ||||
---|---|---|---|---|
include array of objects The repository properties and values to include. All of these properties must match for the condition to pass. | ||||
Properties of |
Nom, Type, Description |
---|
name string ObligatoireThe name of the repository property to target |
property_values array of strings ObligatoireThe values to match for the repository property |
source string The source of the repository property. Defaults to 'custom' if not specified. Peut être: |
exclude
array of objects The repository properties and values to exclude. The condition will not pass if any of these properties match.
Properties of exclude
Nom, Type, Description |
---|
name string ObligatoireThe name of the repository property to target |
property_values array of strings ObligatoireThe values to match for the repository property |
source string The source of the repository property. Defaults to 'custom' if not specified. Peut être: |
rules
array of objects An array of rules within the ruleset.
Can be one of these objects:
Nom, Type, Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
creation object ObligatoireOnly allow users with bypass permission to create matching refs. | |||||||||||||
Properties of |
Nom, Type, Description |
---|
type string ObligatoireValue: |
update
object ObligatoireOnly allow users with bypass permission to update matching refs.
Properties of update
Nom, Type, Description | ||
---|---|---|
type string ObligatoireValue: | ||
parameters object | ||
Properties of |
Nom, Type, Description |
---|
update_allows_fetch_and_merge boolean ObligatoireBranch can pull changes from its upstream repository |
deletion
object ObligatoireOnly allow users with bypass permissions to delete matching refs.
Properties of deletion
Nom, Type, Description |
---|
type string ObligatoireValue: |
required_linear_history
object ObligatoirePrevent merge commits from being pushed to matching refs.
Properties of required_linear_history
Nom, Type, Description |
---|
type string ObligatoireValue: |
required_deployments
object ObligatoireChoose which environments must be successfully deployed to before refs can be pushed into a ref that matches this rule.
Properties of required_deployments
Nom, Type, Description | ||
---|---|---|
type string ObligatoireValue: | ||
parameters object | ||
Properties of |
Nom, Type, Description |
---|
required_deployment_environments array of strings ObligatoireThe environments that must be successfully deployed to before branches can be merged. |
required_signatures
object ObligatoireCommits pushed to matching refs must have verified signatures.
Properties of required_signatures
Nom, Type, Description |
---|
type string ObligatoireValue: |
pull_request
object ObligatoireRequire all commits be made to a non-target branch and submitted via a pull request before they can be merged.
Properties of pull_request
Nom, Type, Description | |||||||
---|---|---|---|---|---|---|---|
type string ObligatoireValue: | |||||||
parameters object | |||||||
Properties of |
Nom, Type, Description |
---|
allowed_merge_methods array of strings When merging pull requests, you can allow any combination of merge commits, squashing, or rebasing. At least one option must be enabled. |
dismiss_stale_reviews_on_push boolean ObligatoireNew, reviewable commits pushed will dismiss previous pull request review approvals. |
require_code_owner_review boolean ObligatoireRequire an approving review in pull requests that modify files that have a designated code owner. |
require_last_push_approval boolean ObligatoireWhether the most recent reviewable push must be approved by someone other than the person who pushed it. |
required_approving_review_count integer ObligatoireThe number of approving reviews that are required before a pull request can be merged. |
required_review_thread_resolution boolean ObligatoireAll conversations on code must be resolved before a pull request can be merged. |
required_status_checks
object ObligatoireChoose which status checks must pass before the ref is updated. When enabled, commits must first be pushed to another ref where the checks pass.
Properties of required_status_checks
Nom, Type, Description | ||||||||
---|---|---|---|---|---|---|---|---|
type string ObligatoireValue: | ||||||||
parameters object | ||||||||
Properties of |
Nom, Type, Description | |||
---|---|---|---|
do_not_enforce_on_create boolean Allow repositories and branches to be created if a check would otherwise prohibit it. | |||
required_status_checks array of objects ObligatoireStatus checks that are required. | |||
Properties of |
Nom, Type, Description |
---|
context string ObligatoireThe 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 ObligatoireWhether 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 ObligatoirePrevent users with push access from force pushing to refs.
Properties of non_fast_forward
Nom, Type, Description |
---|
type string ObligatoireValue: |
commit_message_pattern
object ObligatoireParameters to be used for the commit_message_pattern rule
Properties of commit_message_pattern
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
commit_author_email_pattern
object ObligatoireParameters to be used for the commit_author_email_pattern rule
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
committer_email_pattern
object ObligatoireParameters to be used for the committer_email_pattern rule
Properties of committer_email_pattern
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
branch_name_pattern
object ObligatoireParameters to be used for the branch_name_pattern rule
Properties of branch_name_pattern
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
tag_name_pattern
object ObligatoireParameters to be used for the tag_name_pattern rule
Properties of tag_name_pattern
Nom, Type, Description | |||||
---|---|---|---|---|---|
type string ObligatoireValue: | |||||
parameters object | |||||
Properties of |
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 ObligatoireThe operator to use for matching. Peut être: |
pattern string ObligatoireThe pattern to match with. |
workflows
object ObligatoireRequire all changes made to a targeted branch to pass the specified workflows before they can be merged.
Properties of workflows
Nom, Type, Description | |||||||||
---|---|---|---|---|---|---|---|---|---|
type string ObligatoireValue: | |||||||||
parameters object | |||||||||
Properties of |
Nom, Type, Description | |||||
---|---|---|---|---|---|
do_not_enforce_on_create boolean Allow repositories and branches to be created if a check would otherwise prohibit it. | |||||
workflows array of objects ObligatoireWorkflows that must pass for this rule to pass. | |||||
Properties of |
Nom, Type, Description |
---|
path string ObligatoireThe path to the workflow file |
ref string The ref (branch or tag) of the workflow file to use |
repository_id integer ObligatoireThe ID of the repository where the workflow is defined |
sha string The commit SHA of the workflow file to use |
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 »
Exemple de requête
curl -L \
-X PUT \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2022-11-28" \
http(s)://HOSTNAME/api/v3/orgs/ORG/rulesets/RULESET_ID \
-d '{"name":"super cool ruleset","target":"branch","enforcement":"active","bypass_actors":[{"actor_id":234,"actor_type":"Team","bypass_mode":"always"}],"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"}}]}'
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",
"bypass_mode": "always"
}
],
"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"
}
}
],
"node_id": "RRS_lACkVXNlcgQB",
"_links": {
"self": {
"href": "https://HOSTNAME/orgs/my-org/rulesets/21"
},
"html": {
"href": "https://github.com/organizations/my-org/settings/rules/21"
}
},
"created_at": "2023-08-15T08:43:03Z",
"updated_at": "2023-09-23T16:29:47Z"
}
Delete an organization repository ruleset
Delete a ruleset for an organization.
Jetons d’accès affinés pour « Delete an organization repository ruleset »
Ce point de terminaison fonctionne avec les types de jetons précis suivants:
- Jetons d’accès utilisateur d’application GitHub
- Jetons d’accès d’installation d’application GitHub
- Jetons d’accès personnel affiné
Le jeton précis doit avoir l’ensemble d’autorisations suivant:
- "Administration" organization permissions (write)
Paramètres pour « Delete an organization repository ruleset »
Nom, Type, Description |
---|
accept string Setting to |
Nom, Type, Description |
---|
org string ObligatoireThe organization name. The name is not case sensitive. |
ruleset_id integer ObligatoireThe 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 »
Exemple de requête
curl -L \
-X DELETE \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2022-11-28" \
http(s)://HOSTNAME/api/v3/orgs/ORG/rulesets/RULESET_ID
Response
Status: 204