Diese Version von GitHub Enterprise Server wurde eingestellt am 2025-06-19. Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. Für bessere Leistung, verbesserte Sicherheit und neue Features aktualisiere auf die neueste Version von GitHub Enterprise Server. Wende dich an den GitHub Enterprise-Support, um Hilfe zum Upgrade zu erhalten.
REST-API-Endpunkte für Regelsuiten
Verwenden Sie die REST-API zur Verwaltung von Regelsammlungen für Repositorys.
List repository rule suites
Lists suites of rule evaluations at the repository level. For more information, see "Managing rulesets for a repository."
Differenzierte Zugriffstoken für "List repository rule suites"
Dieser Endpunkt funktioniert mit den folgenden differenzierten Tokentypen.:
- GitHub-App-Benutzerzugriffstoken
 - Zugriffstoken für GitHub App-Installation
 - Differenzierte persönliche Zugriffstoken
 
Das differenzierte Token muss einen der folgenden Berechtigungssätze aufweisen.:
- "Administration" repository permissions (write)
 
Parameter für „List repository rule suites“
| Name, type, BESCHREIBUNG | 
|---|
accept string Setting to   | 
| Name, type, BESCHREIBUNG | 
|---|
owner string ErforderlichThe account owner of the repository. The name is not case sensitive.  | 
repo string ErforderlichThe name of the repository without the   | 
| Name, type, BESCHREIBUNG | 
|---|
ref string The name of the ref. Cannot contain wildcard characters. When specified, only rule evaluations triggered for this ref will be returned.  | 
time_period string The time period to filter by. For example,  Standard:  Kann eine der Folgenden sein:   | 
actor_name string The handle for the GitHub user account to filter on. When specified, only rule evaluations triggered by this actor will be returned.  | 
rule_suite_result string The rule suite results to filter on. When specified, only suites with this result will be returned. Standard:  Kann eine der Folgenden sein:   | 
per_page integer The number of results per page (max 100). For more information, see "Using pagination in the REST API." Standard:   | 
page integer The page number of the results to fetch. For more information, see "Using pagination in the REST API." Standard:   | 
HTTP-Antwortstatuscodes für „List repository rule suites“
| Statuscode | BESCHREIBUNG | 
|---|---|
200 | OK  | 
404 | Resource not found  | 
500 | Internal Error  | 
Codebeispiele für „List repository rule suites“
Anforderungsbeispiel
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/repos/OWNER/REPO/rulesets/rule-suitesResponse
Status: 200[
  {
    "id": 21,
    "actor_id": 12,
    "actor_name": "octocat",
    "before_sha": "893f768e172fb1bc9c5d6f3dd48557e45f14e01d",
    "after_sha": "dedd88641a362b6b4ea872da4847d6131a164d01",
    "ref": "refs/heads/i-see-everything",
    "repository_id": 404,
    "repository_name": "octo-repo",
    "pushed_at": "2023-07-06T08:43:03Z",
    "result": "bypass"
  },
  {
    "id": 25,
    "actor_id": 11,
    "actor_name": "not-octocat",
    "before_sha": "48994e4e01ccc943624c6231f172702b82b233cc",
    "after_sha": "ecfd5a1025fa271a33ca5608d089476a2df3c9a1",
    "ref": "refs/heads/i-am-everything",
    "repository_id": 404,
    "repository_name": "octo-repo",
    "pushed_at": "2023-07-07T08:43:03Z",
    "result": "pass",
    "evaluation_result": "fail"
  }
]Get a repository rule suite
Gets information about a suite of rule evaluations from within a repository. For more information, see "Managing rulesets for a repository."
Differenzierte Zugriffstoken für "Get a repository rule suite"
Dieser Endpunkt funktioniert mit den folgenden differenzierten Tokentypen.:
- GitHub-App-Benutzerzugriffstoken
 - Zugriffstoken für GitHub App-Installation
 - Differenzierte persönliche Zugriffstoken
 
Das differenzierte Token muss einen der folgenden Berechtigungssätze aufweisen.:
- "Administration" repository permissions (write)
 
Parameter für „Get a repository rule suite“
| Name, type, BESCHREIBUNG | 
|---|
accept string Setting to   | 
| Name, type, BESCHREIBUNG | 
|---|
owner string ErforderlichThe account owner of the repository. The name is not case sensitive.  | 
repo string ErforderlichThe name of the repository without the   | 
rule_suite_id integer ErforderlichThe unique identifier of the rule suite result. To get this ID, you can use GET /repos/{owner}/{repo}/rulesets/rule-suites for repositories and GET /orgs/{org}/rulesets/rule-suites for organizations.  | 
HTTP-Antwortstatuscodes für „Get a repository rule suite“
| Statuscode | BESCHREIBUNG | 
|---|---|
200 | OK  | 
404 | Resource not found  | 
500 | Internal Error  | 
Codebeispiele für „Get a repository rule suite“
Anforderungsbeispiel
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/repos/OWNER/REPO/rulesets/rule-suites/RULE_SUITE_IDResponse
Status: 200{
  "id": 21,
  "actor_id": 12,
  "actor_name": "octocat",
  "before_sha": "893f768e172fb1bc9c5d6f3dd48557e45f14e01d",
  "after_sha": "dedd88641a362b6b4ea872da4847d6131a164d01",
  "ref": "refs/heads/i-see-everything",
  "repository_id": 404,
  "repository_name": "octo-repo",
  "pushed_at": "2023-07-06T08:43:03Z",
  "result": "bypass",
  "evaluation_result": "fail",
  "rule_evaluations": [
    {
      "rule_source": {
        "type": "ruleset",
        "id": 2,
        "name": "Author email must be a GitHub email address"
      },
      "enforcement": "active",
      "result": "pass",
      "rule_type": "commit_author_email_pattern"
    },
    {
      "rule_source": {
        "type": "protected_branch"
      },
      "enforcement": "active",
      "result": "fail",
      "rule_type": "pull_request",
      "details": "Changes must be made through a pull request."
    },
    {
      "rule_source": {
        "type": "ruleset",
        "id": 3,
        "name": "Evaluate commit message pattern"
      },
      "enforcement": "evaluate",
      "result": "fail",
      "rule_type": "commit_message_pattern"
    }
  ]
}