marge-bot
marge-bot is a merge bot for advanced merge request workflows on GitLab. Marge helps keep your main branch green, and comes with a set of features to make managing merge requests at scale easier. It improves on GitHub's merge queue and GitLab's merge train workflows by automatically handling rebases and merges, batching merge requests, and more.
Marge-bot offers a simple workflow: when a merge request is ready, just assign it to the marge-bot user, and let her do all the rebase-wait-retry for you. If anything goes wrong (merge conflicts, tests that fail, etc.) she'll leave a message on the merge request, so you'll get notified. Marge-bot can handle an adversarial environment where some developers prefer to merge their own changes, so the barrier for adoption is really low.
Whether marge-bot will or will not wait for pipeline to succeed depends on the value of "Pipelines must succeed" setting in your project. It is available in all Gitlab versions, and should not be a barrier.
Since she is at it, she can optionally provide some other goodies like tagging
of commits (e.g. Reviewed-by: ...) or preventing merges during certain hours.
1 maintainer
Release files for marge-bot 1.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| marge_bot-1.3.2.tar.gz | 276.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| marge_bot-1.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 319.9 kB
Release files / marge_bot-1.3.2.tar.gz
| Download URL | marge_bot-1.3.2.tar.gz |
|---|---|
| Size | 276.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b82b4e3c84c8ae248699eabceeec8af7dcc45b985810e0c79b930c52492664b
|
|
BLAKE2b-256 checksum How to use checksums |
df2a7bece429c44c53fb83045e50ec2cd6ba7274bfaa787a4cb6442c57f74e1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitLab CI/CD, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / marge_bot-1.3.2-py3-none-any.whl
| Download URL | marge_bot-1.3.2-py3-none-any.whl |
|---|---|
| Size | 43.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb5cf5ab85aefcab44a5317b50854b972a6aa484b9784b1a9f6c8483df8afd40
|
|
BLAKE2b-256 checksum How to use checksums |
5f38405ee952a5eafee8b75c09d21f497238c6c058d460a8d279dc29b028f43d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitLab CI/CD, verified by PyPI on Aug 15, 2026.
Transparency log
