Repository navigation
Replies: 1 comment
|
I do not vibecode myself and while I don't intentionally make it harder to use my packages together with a LLM, I also won't add any features specifically to better support LLMs. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Thanks for Magit and forge! Appreciate it and the hard work that goes into maintaining your regular release schedule!
My AI workflow now is similar to my "people" workflow. I create an issue on GitHub, assign it to a person or to copilot and review the PR that comes out. Most of this process can now be managed by forge.
The one thing I still need to use GitHub.com website for is to assign an issue to copilot as copilot is not a member of a repo and does not show up in the Assignees: field, it's a special thing. Github released an API for this before christmas
https://github.blog/changelog/2025-12-03-assign-issues-to-copilot-using-the-api/
https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/create-a-pr#assigning-an-issue-to-copilot-via-the-github-api
Thought this could be useful to others as well so I humbly suggest and idea for a feature. It is likely that a similar workflow will appear on other forge's as well as AI development becomes even more prevalent.
All reactions