You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Multica for ticket management, have it complete tasks, and submit code to the main repository via fork & PR.
After I review the code, I can @agent in a Multica issue comment to request revisions.
I tried describing the process in issues, and even created a process skill to add to the agent, but the results weren't ideal. For example, it doesn't fork, doesn't submit PRs, etc. Is there a better way to achieve a similar workflow?
Hi, i add repo in this, but agent work not good, even though I described the complete workflow in the issue.
I also tried creating a github-workflow skill, but the results weren't great either. I wonder if there are any other suggestions?
@seepine very curious about your experience! I was actually planning to put my entire KB in GitHub for active memory management purposes. What is not working well for you with the Github repo?
I created a custom github app and wired it up to Multica but it seems quite complicated and then pushes and PRs are from a "Bot" that causes other issues, i am curious how others have Multica gain access to private repo's to pull, commit and raise PR's etc?
I'm building out an entire Ship product to handle all of this. First three phases are posted in PR's but I'll have everything else tested and posted in the next day or two.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
My current desired workflow is:
Use Multica for ticket management, have it complete tasks, and submit code to the main repository via fork & PR.
After I review the code, I can @agent in a Multica issue comment to request revisions.
I tried describing the process in issues, and even created a process skill to add to the agent, but the results weren't ideal. For example, it doesn't fork, doesn't submit PRs, etc. Is there a better way to achieve a similar workflow?
All reactions