almalinux/pungi
15
2
Fork 0
Code Issues Pull requests Releases Activity Actions

Add implementation plan for the autopatch pipeline #21

Merged
soksanichenko merged 1 commit from autopatch-plan-b into master 2026-09-30 12:00:55 +00:00
Conversation 0 Commits 1 Files changed 1 +2926
soksanichenko commented 2026-09-30 11:46:18 +00:00
Owner
Copy link

Summary

This PR adds docs/superpowers/plans/2026-09-30-pungi-autopatch-pipeline.md, the implementation plan for plan B of the pungi autopatch design (docs/superpowers/specs/2026-09-29-pungi-autopatch-design.md). The plan covers the autopatch-pungi CLI, the Forgejo workflows, and the integration dry runs against the real repositories. This is documentation only.

The plan is already implemented and merged in autopatch/pungi#1. During implementation, the task reviews and the final review changed some details compared with this document. The main changes:

  • Git errors redact the token. Git authenticates through an http.<forge>/.extraHeader header in the environment, never through URLs.
  • The sync-branch state counts only while an open PR exists. The changelog baseline is main.
  • Autopatch-Config records the last commit that touched config.yaml or files/.
  • A missing token without --dry-run exits with code 2.
  • Publish failures and Fedora-side failures open issues. Forge API errors count as fetch failures.
  • Released .alma. changelog entries are carried over into the next release.

The code in autopatch/pungi is the source of truth. The plan is kept here as the design record.

🤖 Generated with Claude Code

## Summary This PR adds `docs/superpowers/plans/2026-09-30-pungi-autopatch-pipeline.md`, the implementation plan for plan B of the pungi autopatch design (`docs/superpowers/specs/2026-09-29-pungi-autopatch-design.md`). The plan covers the `autopatch-pungi` CLI, the Forgejo workflows, and the integration dry runs against the real repositories. This is documentation only. The plan is already implemented and merged in autopatch/pungi#1. During implementation, the task reviews and the final review changed some details compared with this document. The main changes: - Git errors redact the token. Git authenticates through an `http.<forge>/.extraHeader` header in the environment, never through URLs. - The sync-branch state counts only while an open PR exists. The changelog baseline is `main`. - `Autopatch-Config` records the last commit that touched `config.yaml` or `files/`. - A missing token without `--dry-run` exits with code 2. - Publish failures and Fedora-side failures open issues. Forge API errors count as fetch failures. - Released `.alma.` changelog entries are carried over into the next release. The code in autopatch/pungi is the source of truth. The plan is kept here as the design record. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Plan B of the pungi autopatch design: the autopatch-pungi CLI, the
Forgejo workflows, and the integration dry runs against the real
repositories, including the lessons from the rebase to 4.14.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
soksanichenko deleted branch autopatch-plan-b 2026-09-30 12:00:55 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
almalinux/pungi!21
No description provided.