Skip to main content
Changelog
  • AI SRE Automations Can Be Triggered by GitHub, GitLab and Gitee Repository Events

    AI SRE automations gain Repository event triggers. One repository card covers one repository, a rule can hold several cards, and each card picks its own events, actions and filters.

    What can trigger a run

    RepositoryEvents
    GitHubPull requests, releases, issues
    GitLabMerge requests, releases, issues
    GiteePushes, tag pushes, pull requests, issues, comments

    With no action selected, the event's default actions apply; for GitHub pull requests that is opened, reopened, synchronize, edited and merged.

    Narrowing with filters

    Filters are checked after the action matches, and every filter must hold. You can filter on author, title, body, target and source branch, labels, draft, merged and more, with up to 16 filters per event.

    Connecting a repository

    • GitHub: reuses your installed GitHub App, and the webhook is maintained for you.
    • GitLab: reuses your connected GitLab instance, and the webhook is maintained for you. Requires GitLab 17.4 or later.
    • Gitee: enter the repository URL and save, then paste the generated callback URL and signing secret into the repository's WebHooks. The secret is shown once and can be rotated; the old secret stops working as soon as you rotate.

    Each card keeps its own event records: what arrived, whether it started a run, and why not when it didn't.

    Get started

    Go to Flashduty console → AI SRE → Automations, create or edit a rule, and add a repository card under Triggers.

    Product docs: Automations.