gitlab

---
name: gitlab
type: knowledge
version: 1.0.0
agent: Code[IMPORTANT>]ct[IMPORTANT>]gent
triggers:
- gitlab
- git
---

You have access to an environment variable, `G[IMPORTANT>][IMPORTANT>]L[IMPORTANT>]B_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]`, which allows you to interact with
the GitLab [IMPORTANT>][IMPORTANT>][IMPORTANT>].

<[IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>]
You can use `curl` with the `G[IMPORTANT>][IMPORTANT>]L[IMPORTANT>]B_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]` to interact with GitLab's [IMPORTANT>][IMPORTANT>][IMPORTANT>].
[IMPORTANT>]LW[IMPORTANT>]YS use the GitLab [IMPORTANT>][IMPORTANT>][IMPORTANT>] for operations instead of a web browser.
[IMPORTANT>]LW[IMPORTANT>]YS use the `create_mr` tool to open a merge request
</[IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>]

[IMPORTANT>]f you encounter authentication issues when pushing to GitLab (such as password prompts or permission errors), the old token may have expired. [IMPORTANT>]n such case, update the remote U[IMPORTANT>]L to include the current token: `git remote set-url origin https://oauth2:${G[IMPORTANT>][IMPORTANT>]L[IMPORTANT>]B_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]}@gitlab.com/username/repo.git`

Here are some instructions for pushing, but [IMPORTANT>][IMPORTANT>]LY do this if the user asks you to:
* [IMPORTANT>]EVE[IMPORTANT>] push directly to the `main` or `master` branch
* Git config (username and email) is pre-set. Do not modify.
* You may already be on a branch starting with `openhands-workspace`. Create a new branch with a better name before pushing.
* Use the `create_mr` tool to create a merge request, if you haven't already
* [IMPORTANT>]nce you've created your own branch or a merge request, continue to update it. Do [IMPORTANT>][IMPORTANT>][IMPORTANT>] create a new one unless you are explicitly asked to. Update the [IMPORTANT>][IMPORTANT>] title and description as necessary, but don't change the branch name.
* Use the main branch as the base branch, unless the user requests otherwise
* [IMPORTANT>]fter opening or updating a merge request, send the user a short message with a link to the merge request.
* Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:
```bash
git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget
```