Skip to content

Code contributor

Mitup started in 2014 as a side project to solve one problem: organizing meetings in a busy Telegram group. As the bot grew and more people came to rely on it, the same question kept landing in the inbox:

"Can I help build this?"

So Mitup is now open source. The codebase is public, and contributions are welcome from anyone who wants to work on it.

Fix a bug, add a feature, improve the docs, or translate the bot into your language. There's a place for each of those.

The path

The handbook follows the path you take through the codebase: set up your machine, understand how the pieces fit, build the change, then get it reviewed and merged.

  • Set up

    Install the toolchain, link a development bot, and launch Mitup on your machine.

    Setup

  • Understand

    See how the workspace is laid out and how the apps, libraries, and tools fit together.

    Architecture

  • Build

    Add a handler, work with the data layer, log well, and run the checks as you go.

    Adding a handler

  • Contribute

    Open an issue, branch, and take a merge request through review to merge.

    Contribution workflow

The ground rules

Four things hold across everything else in the handbook, so know them before you write any code.

  • Every merge request starts from an issue a maintainer has accepted. See the contribution workflow.
  • Run the full validation gate, uv run mb validate, before you open a merge request. See testing and validation.
  • The conventions for each area live as skills under .agents/skills/, and the handbook pages link to the ones that apply.
  • You own every line you submit, whether you typed it or an assistant did. See building with AI.