Working with Support for GitHub Actions

Learn how GitHub-Support can assist with GitHub Actions

In diesem Artikel

You can contact GitHub-Support for assistance with GitHub Actions.

Providing diagnostic and troubleshooting information

The contents of private and internal repositories are not visible to GitHub-Support, so GitHub-Support may request additional information to understand the complete context of your inquiry and reproduce any unexpected behavior. You can accelerate the resolution of your inquiry by providing this information when you initially raise a ticket with GitHub-Support.

Some information that GitHub-Support will request can include, but is not limited to, the following:

  • The URL of the workflow run.

    For example: https://DOMAIN/ORG/REPO/actions/runs/0123456789

  • The workflow .yml file(s) attached to the ticket as .txt files. For more information about workflows, see "Informationen zu Workflows."

  • A copy of your workflow run logs for an example workflow run failure. For more information about workflow run logs, see "Using workflow run logs."

  • A copy of your runner logs, which can be found under the _diag folder within the runner. For more information about self-hosted runners, see "Überwachen und Behandeln von Problemen mit selbstgehosteten Runnern."

    Self-hosted runner log file names are be formatted: Runner_YYYY####-xxxxxx-utc.log and Worker_YYYY####-xxxxxx-utc.log.

Note: Attach files to your support ticket by changing the file's extension to .txt or .zip. If you include textual data such as log or workflow file snippets inline in your ticket, ensure they are formatted correctly as Markdown code blocks. For more information about proper Markdown formatting, see "Grundlegende Schreib- und Formatierungssyntax."

If the information you provide is unreadable due to the loss of formatting by improper Markdown syntax, GitHub-Support may request that resubmit the information either as an attachment or with the correct Markdown formatting.

Warning: Ensure all files and text provided to GitHub-Support have been properly redacted to remove sensitive information such as tokens and other secrets.

Depending on the nature of your inquiry, GitHub-Support may also request that you generate and upload a support bundle for further review and analysis. For more information about providing data to GitHub-Support and support bundles, see "Providing data to GitHub Support (Bereitstellen von Daten für GitHub Support)."

Ephemeral Runner Application Log Files

GitHub-Support may request the runner application log files from ephemeral runners. GitHub expects and recommends that you have implemented a mechanism to forward and preserve the runner application log files from self-hosted ephemeral runners. For more information about runner application log files and troubleshooting self-hosted runners, see "Überwachen und Behandeln von Problemen mit selbstgehosteten Runnern."

Actions Runner Controller

If you are using Actions Runner Controller (ARC), GitHub-Support may ask you to submit the complete logs for the controller, listeners, and runner pods. For more information about collecting Actions Runner Controller's logs, see "Problembehandlung bei Actions Runner Controller-Fehlern."

For more information about the scope of support for Actions Runner Controller, see "Informationen zur Unterstützung von Actions Runner Controller."

CodeQL and GitHub Actions

If you are requesting assistance with a CodeQL-Analyseworkflow, GitHub-Support may request a copy of the CodeQL debugging artifacts. For more information about debugging artifacts for a CodeQL-Analyseworkflow, see "Protokolle sind nicht detailliert genug."

To provide the debugging artifacts to GitHub-Support, please download the CodeQL debugging artifacts from a sample workflow run and attach it to your ticket as a .zip file. For more information on downloading workflow artifacts, see "Herunterladen von Workflowartefakten."

If the CodeQL debugging artifacts .zip file is too large to upload to the ticket, please advise GitHub-Support, and we will work with you to determine the next steps.

Scope of support

Wenn deine Supportanfrage außerhalb des Geltungsbereichs liegt, bei dem unser Team dir helfen kann, können wir dir die nächsten Schritte empfehlen, damit du deinen Issue außerhalb von GitHub-Support beheben kannst. Deine Supportanfrage liegt möglicherweise nicht im Zuständigkeitsbereich von GitHub-Support, wenn es in erster Linie um die folgenden Themen geht:

  • Integrationen von Drittanbietern, z. B. Jira
  • Enterprise Cloud Importer (nur bei von Experten geleiteten Migrationen verfügbar)
  • Hardwareeinrichtung
  • CI/CD, z. B. Jenkins
  • Schreiben von Skripts
  • Konfiguration externer Authentifizierungssysteme, z. B. SAML-Identitätsanbieter
  • Open Source-Projekte
  • Neue Abfragen für CodeQL schreiben oder debuggen
  • Konfigurationen von Cloudanbietern, z. B. Einrichtung des virtuellen Netzwerks, benutzerdefinierte Firewall oder Proxyregeln.
  • Container-Orchestrierung, z. B. Kubernetes-Setup, Netzwerk usw.
  • Detaillierte Unterstützung bei Workflows und Datenverwaltung
  • BETA-Funktionen. Die Unterstützung für Betafeatures liegt außerhalb des Bereichs von GitHub-Support.

Detaillierte Unterstützung bei Workflows und Datenverwaltung erhalten Sie von GitHub Expert Services, die spezielle Unterstützung bieten, um Ihre Nutzung der Plattform zu optimieren.

Wenn du unsicher bist, ob der Issue außerhalb des Bereiches liegt, öffne ein Ticket, und wir helfen Dir gerne dabei zu bestimmen, wie du am besten fortfährst.