-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Resolver]: Gitlab support #5210
Comments
Hi @josx , we (the current maintainers me and @malhotra5) probably aren't going to work on this ourselves right now (just due to lack of time), but we'd 100% welcome a contribution in this direction! |
Ok, Something that we have to take into account so that it can be done. Any advice? |
Hey @josx! I'd recommend taking a look at The files Unit tests in Lastly, we'd need another workflow definition file similar to |
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This is still on our eventual roadmap |
Hello folks! We started working on this issue here on our forked repo.
The next steps that we think can be correct are:
We worked on this with @cuococarlos, @juanmanueldaza, @josx Let us know if you have any comments and if you think it is the correct approach |
@Orianamartina That's awesome! Please feel free to create a draft PR if you want, it will make it easier to see the diff or comment if needed, although of course it's up to you. |
Hello @neubig, If possible, it would be interesting to make it more generic, I work on opensource projects like Forgejo and Gitea to manage my projects |
Hey @Orianamartina , this sounds awesome, looking forward to it! I think on a high level the plan sounds great. I'd also echo @enyst 's suggestion to feel free to send over a pull request for review sooner rather than later. We can pull on each step of the process as it's finished to keep the code bases in sync and the review process manageable |
Hey, We're working on integrating Gitlab into OpenHands based off of where @Orianamartina left off, however there seems to be one issue that needs to be discussed. Currently, OpenHands primarily works off of "issues to PR/MR" which works well for Github, however Gitlab doesn't have this logic in its |
It would be even more useful to be able to use Gitea as a repository as well. |
Hi @codykociemba , sorry about the late reply! And hmm, that's a bit annoying. I'm not familiar enough (yet) with gitlab webhooks to make an informed decision about this... maybe a cron-job would be simpler, but I'm not really sure. |
Just a quick update, we've modified the project to add Gitlab support, using either Webhook or Gitlab CI/CD to trigger the agent/runtime. We're cleaning up the code a bit before submitting a PR, however if anyone is wanting to dabble with OpenHands yourself using Gitlab, here is the
You'll need to add the following Gitlab CI/CD variables:
Without a Webhook, the agent will only trigger on merge request events with the "fix-me" label. In order to get the agent to trigger on Issues, you'll need to setup a Webhook to trigger a pipeline. The webhook should send the following variables to the pipeline:
|
Sounds great, but when will it be released? Is there an alpha version to experience |
@ChengranYan Here is our initial PR which adds Gitlab support: #6458 |
What problem or use case are you trying to solve?
There are plenty source code in gitlab software in public and private instances. It has a plus is free software.
So would be nice to have resolve issues , Responding to PR Comments, and CI/CD (like github workflow but for gitlab).
Do you have thoughts on the technical implementation?
Additional context
With this feature will enable a complete workflow local or on-premise with free software.
The text was updated successfully, but these errors were encountered: