Skip to content

feat: sign automation commits via the Automation App API #488

Open

Description

@DevSecNinja

Problem

repo-steward is about to require signed commits on the default branch of public repos (DevSecNinja/repo-steward#42). Under that rule, GitHub won't squash-merge a PR that contains unsigned commits unless the person merging is the PR's author, or uses a ruleset bypass.

These automation jobs push unsigned commits as github-actions[bot]. Found in open PRs on 2026-11-12:

  • Central config-sync PRs: aliasaurus, dotfiles, grip-visualizer, home-assistant-config, key-vault-pass, truenas-apps
  • "materialize APM primitives" PRs: .github, ai-toolkit
  • dotfiles' "sign PowerShell scripts" job (for example dotfiles#1010)
  • ai-toolkit's Generate Index job, which commits straight to main on push (ci: check the index on PRs instead of pushing [skip ci] commits ai-toolkit#221 keeps that push)

Renovate isn't affected: its commits are signed, and it auto-merges fine in repos that already require signatures (worldtime, net-worth-calculator, home-assistant-win-companion).

Proposed solution

  • Make the reusable config-sync and apm-materialize workflows commit through the Automation App token with the API (GraphQL createCommitOnBranch, or the Git Data API with the app token). GitHub signs those commits.
  • Do the same for dotfiles' PowerShell signing job and ai-toolkit's Generate Index job, or have them call a shared reusable "signed commit" action.
  • Add a test or check that fails when a reusable workflow uses git commit / git push as github-actions[bot].
  • Copilot coding agent PRs: check whether its commits are signed now; this issue only notes them.

Alternatives considered

  • Leaving the owner bypass to merge these PRs: it works, but every bot PR becomes a manual bypass merge.
  • Leaving signed commits out of the rule for these repos: that weakens the baseline.

Activity

  1. DevSecNinja commented on Nov 16, 2026

    @DevSecNinja
    OwnerAuthor

    Two more config-sync PRs blocked by this on 2026-11-16, both otherwise green and Copilot-reviewed: DevSecNinja/vidaud#186 and DevSecNinja/hadiscover#450. The re-dispatched sync commits are unsigned, and the default-branch ruleset fails with 'Commits must have verified signatures', so each needs the owner's ruleset bypass to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions