The workflow is split into two jobs for least-privilege: 1. 'review' job — runs Claude with read-only permissions (contents: read, id-token: write for AWS OIDC, actions: read). Claude produces a structured JSON review via --json-schema with a 'comments' array and a 'summary' string. Its tools are restricted to read-only operations (Read, LS, Grep, Glob, Task, and various Bash prefixes for common read-only commands). Claude also has access to CI MCP tools to analyze failed workflow runs. 2. 'post' job — only has pull-requests: write. Reads the structured JSON output from the review job and posts inline comments individually (so re-runs only add new comments). Maintains a tracking comment with a <!-- claude-pr-review --> marker that is created on first run and updated in-place on subsequent runs, preserving existing item order, wording, and checkbox state. Posts a notification comment when the tracking comment is updated or left unchanged. Comment deduplication is handled by Claude in the prompt rather than in the posting script, allowing for better semantic understanding of whether two comments address the same issue. The PR number is resolved via github.event.pull_request.number with a fallback to github.event.issue.number for issue_comment events where github.event.pull_request is not populated. The concurrency group uses the same fallback. Co-developed-by: Claude <claude@anthropic.com>
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release
