Hey :wave: `Issue-to-MR` ready-to-use automation....
# proj-automation
m
Hey šŸ‘‹
Issue-to-MR
ready-to-use automation. Need two PRs because I had some problem to install the GITLAB MCP • feat(gitlab-issue-to-mr): add a label-triggered issue-to-MR automation • fix(agent-server): delegate MCP OAuth callback to FastMCP instead of forking it • fix(sdk): require fastmcp=3.2.0 so expired MCP OAuth tokens refresh> cc @elegant-branch-54423 Sorry I re-create the automation instead of using your PR. I had to change a couple of things and it was faster doing so. PS: note that this is still a crono automation.
e
Not a problem and thanks!
Does the Automation Template rely on the user providing a long lived GITHUB_TOKEN as a secret, or does it use the GitLab MCP server?
m
I use the GITLAB MCP server copying what we arw doing with the issue-to-pr automation (for that reason i also have a PR in the sdk) It should work p
šŸ™Œ 1
e
Thanks! I experienced some bugginess with the OAuth-based MCP servers recently (filed a similar bug here #17077). It looks like your fix solves a similar issue!
m
let me look into that šŸ™‚
it seems that your issue is highlighting 2 problems and one is fixed by the PR above. Looking into the second one
@elegant-branch-54423 ok the second issue was just about versions conflicting. Small fix. I added the PR in the thread above.
e
Thanks so much for looking into this! Integrations/MCP Connections are such an important part of users getting value with Automations and Canvas, so it's great we're able to triage and fix things related to the OAuth flow!
@hundreds-twilight-32833 fyi there's some PRs here that need review and merging. Currently OAuth MCP isn't working in Canvas (incl 1.17), and one of these PRs fixes it. You can repro it w/ the GitLab and Atlassian Rovo MCP servers which both use OAuth.
h
Hoping to get them looked at as well as some others for another canvas release
m
Hey, I'm not sure if both fixes were in the sdk version that was released with the agent-canvas
h
It doesn't look like either of the sdk PRs were merged yet. So it'll be SDK merges then bump in canvas then release
šŸ‘ 1
m
@hundreds-twilight-32833 also the extension PR was not merged (the first one)
e
Would love to get these into an upcoming release! šŸ™‚
m
ah ok I will do it today and starting to prepare tht
c
@bland-bear-604 find the issue-to PR/MR automations, and let’s make tiny tweaks. I looked at the video and it uses passive a lot, I’d like the text to say, when meaningful, that OpenHands does the thing, like • ā€œis implementedā€ -> ā€œOpenHands implementsā€ • ā€œis worked onā€ -> ā€œOpenHands works onā€ • -> whether OpenHands should open the request as a draft… etc, as appropriate Note that this doesn’t apply to polling, that can stay passive or whatever, it’s just cron. Generally if the OpenHands agent is doing it, let’s say it’s doing it. Open PR
🐾 1
b
Opened 🐾 Eight small help-text edits across GitHub issue-to-PR and GitLab issue-to-MR. OpenHands now implements, works on, names branches, and opens requests. Polling and behavior stay unchanged. Catalog tests: 143 passed. https://github.com/OpenHands/extensions/pull/831 I left it draft for your HUMAN note.
c
Vasco, I’d love to know if it sounds okay to you
m
LGTM šŸ™‚
smolpaws doing smolpaws things