[GH-ISSUE #411] CI workflow updates to copy notes from fork after merge #153

Open
opened 2026-03-02 04:12:20 +03:00 by kerem · 2 comments
Owner

Originally created by @svarlamov on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/411

We'd love for more open source maintainers (ourselves included) to retain the Git AI notes that come in from forks. This would require updates to our CI actions to copy over the Git AI notes from forks after PRs are merged.

  1. Reference the existing CI logic and templates in src/ci
  2. Support forks in the existing squash/rebase logic (I believe that forks do not currently copy notes in these flows either)
  3. For normal merges (merge commit instead of squash/rebase), detect when we're merging from a fork and copy notes for the commits that we're merging in.
  4. Update CI templates (if necessary, probably not as the templates already trigger on merges)
Originally created by @svarlamov on GitHub (Jan 28, 2026). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/411 We'd love for more open source maintainers (ourselves included) to retain the Git AI notes that come in from forks. This would require updates to our CI actions to copy over the Git AI notes from forks after PRs are merged. 1. Reference the existing CI logic and templates in `src/ci` 2. Support forks in the existing squash/rebase logic (I believe that forks do not currently copy notes in these flows either) 3. For normal merges (merge commit instead of squash/rebase), detect when we're merging from a fork and copy notes for the commits that we're merging in. 4. Update CI templates (if necessary, probably not as the templates already trigger on merges)
Author
Owner

@svarlamov commented on GitHub (Feb 8, 2026):

Related to #334

<!-- gh-comment-id:3865998600 --> @svarlamov commented on GitHub (Feb 8, 2026): Related to #334
Author
Owner

@svarlamov commented on GitHub (Feb 13, 2026):

Following up on our discord chat, @Ngineer101 is taking this on

<!-- gh-comment-id:3899675680 --> @svarlamov commented on GitHub (Feb 13, 2026): Following up on our discord chat, @Ngineer101 is taking this on
Sign in to join this conversation.
No milestone
No project
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
starred/git-ai#153
No description provided.