Skip to main content

Synchronise your GitLab issues to a todo.txt file

Project description

gitlab-todotxt

A tool to synchronize GitLab issues to a todo.txt file.

When started, gitlab-todotxt will read the configuration file, load all issues, and write them into a todo.txt-type file of your choice.

Configuration

gitlab-todotxt requires a configuration file. It expects the configuration file by default in ~/.config/gitlab-todotxt/gitlab-todotxt.conf.

Each GitLab configuration is a separate section in the configuration file. The title of that section must not contain any spaces.

This is an example configuration:

[example.org]
url = https://gitlab.example.org
token = your-access-token
projects = project1, project2
unassigned = no

The minimal required options are:

  • url, the URL to the GitLab instance you are using.
  • token, your personal API access token.
  • file, the file where to write the tasks into.

Additional options are:

  • namespaces, the list of namespaces to consider when importing issues. Only namespaces on this list will be considered when imporrting issues. When left empty (the default), all accessible namespaces are considered.
  • projects, the list of projects to consider when importing issues. Only projects on this list will be considered when importing issues. When left empty (the default), all accessible projects are considered.
  • users, the list of users to consider when importing issues. Only issues that are assigned to a user of this list (or to yourself) are considered for importing. When empty (the default) no issues, unless assigned to you, are imported.
  • labels, the list of labels of which an issue must have at least one to be included in the import.
  • unassigned, whether or not unassigned issues should be imported.
  • labels-are-projects, whether or not labels of issues should be added as project tags.
  • milestone-prefix, the prefix you would like to have before the milestone element, if there is a milestone. Defaults to milestone:.
  • format, the format to write the todo.txt task in. See below for details.

Format Option

The format option in the configuration can be used to customize in what form your todo.txt tasks are written to file.

The default is

{delegate} {title} {due} {project} {milestone} {estimate} {spent} {url}

These are also all possible fields:

  • delegate: if an issue is assigned to someone else than you, @delegated will be written in this place, followed by to: and the username of those the issue is assigned to
  • title: the title of the issue,
  • due: the due date of the issue or, if there is none, the due date of the milestone this task belongs to (if any); in form of a due: tag.
  • project: the project this task belongs to.
  • spent: the time spent on the task.
  • estimate: the estimated time for the task.
  • milestone: the milestone of the issue.
  • url: the URL to the actual issue at the GitLab website

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

gitlab-todotxt-0.2.0.tar.gz (7.5 kB view details)

Uploaded Source

Built Distribution

gitlab_todotxt-0.2.0-py3-none-any.whl (7.8 kB view details)

Uploaded Python 3

File details

Details for the file gitlab-todotxt-0.2.0.tar.gz.

File metadata

  • Download URL: gitlab-todotxt-0.2.0.tar.gz
  • Upload date:
  • Size: 7.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.1 CPython/3.10.7

File hashes

Hashes for gitlab-todotxt-0.2.0.tar.gz
Algorithm Hash digest
SHA256 035ccc18498ecbcd1ad20a351104812e4f1beff12049d1d29fc4f41e972b1b83
MD5 2d27cef11a0cda72cb051f5843961d64
BLAKE2b-256 d73f8b913959282473ebcaa4ca382cdfc5cddc3b2febe0cba720a64d01ace215

See more details on using hashes here.

File details

Details for the file gitlab_todotxt-0.2.0-py3-none-any.whl.

File metadata

File hashes

Hashes for gitlab_todotxt-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 3d7a1ced54c6b6c1d6ea59314c63862c06c232cb65c18002841a2fc5bedadab0
MD5 e2a8bbafaa0f154a63e39d7eed550798
BLAKE2b-256 a1fbc9f07c3685a80d5fd4114f66fe68c18988ac2acc357a5641eb120f0a97da

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page