Feedback from a prospect: It would be great to have our current Automation templates to also support GitLab out of the box

Sounds good and more generally do you have a suggestion for how we should handle and organized requests like this? I think we have a system for ohe and existing customers but I don't know if we have a system for things that are mainly in the realm of OSS

I think a simple answer is creating an issue in the OpenHands/OpenHands repo, have it synced from GitHub<>Linear, and then optionally tagging it w/ a customer in our internal Linear system.

It sounds like maybe these are two sources of data, two entries into the system: • customer request tag in Linear • user request label in GitHub I mean, maybe what we can do is decide a label for “we know this is a user request”

works for me! a user-request label is just as good.

Yeah @calm-artist-7206 as we discussed before we’re getting more and more issues that are not from actual users, so even just knowing that it’s from a user would also be helpful

Hey, I tested it and it seems that there is a problem in a very specific user case: github.com/OpenHands/software-agent-sdk/issues/4818. But this really depends on how you install packages. @elegant-branch-54423 Are you using the agent-canvas with docker BE when you were testing it? Because I think that I found this problem because I was using the agent-server locally. Another point,

GitLab issue to PM agent

seems to be in the

beta

section. Did you want to have it in the

Start from a proven workflow

. Or we want to change the name of these sectins?

I ran into this issue running Canvas locally via an NPM install. Not running in docker. I do not have that specific

GitLab Issue to MR Agent

in Beta (see screenshot). This is from the latest release

1.16

• I actually have an open PR to add this automation: github.com/OpenHands/extensions/pull/525

Ah yes but i started a version using your extension (i hope. Let me double check)

(Also, for consistency, can we remove “Agent” from the automation title, as we typically name automations after the job to be done, not the agents that perform them)

So my question was: do you want it in beta or in proven-workflows? Do you mind if I push to your branch?

Let’s do beta since it’s not extensively tested yet

Beta makes sense to me. Vasco, I think my PR might need some tidying up -- specifically, it might need a corresponding

gitlab-issue-to-mr

skill to model itself after the

github-issue-to-pr

automation template. I will try and do that today.

If you want to turn that over to Vasco he could probably take it over the line

Would be happy to! @modern-fireman-99755 if you have cycles, that is.

Do you have tickets for them? Is there a deadline?

There's actually an existing ticket (I just re-opened): github.com/OpenHands/extensions/issues/443 • I started the PR on my own time because I had a prospect interested in GitLab-centric Automation Templates. • It's not urgent, but would be great to get within the next week.

Ok 👍 I'm out next week. So I will try to do it in the next couple of days