Daan De Meyer
3a76c0959f
Address feedback from facebook/bpfilter#472: - Fix setFailed error message counting file-level comments (without line numbers) that are intentionally skipped, use inlineComments.length instead of comments.length - Fix double severity prefix in inline comments: the prompt told Claude to prefix body with **must-fix**/etc but the post job also prepended "Claude: ", producing "Claude: **must-fix**: ...". Now the prompt says not to prefix and the post job adds "Claude **severity**: " using the structured severity field - Move error tracking instructions to a top-level section after all phases so they apply to all runs, not just the first run - Clarify that line is optional: use "should be" instead of "must be" and document that omitting line still surfaces the comment in the tracking comment summary - Distinguish cancelled vs failed in tracking comment message - Add side: "RIGHT" and subject_type: "line" to createReviewComment per GitHub API recommendations - Downgrade partial inline comment posting failures to warnings; only fail the job when no comments at all could be posted Co-developed-by: Claude Opus 4.6 <noreply@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