DATALAD-CREATE-SIBLING-GITEA(1)

💅 datalad create-sibling-gitea

okay so bestie, welcome to the datalad create-sibling-gitea page — it lives in the General Commands Manual and it's genuinely one of the cutest little commands in the whole family. settle in, grab a strawberry drink 🍓, and let's get you a repo on Gitea.

---

✨ NAME ✨

datalad create-sibling-gitea — create a dataset sibling on a Gitea site. that's it, that's the whole job, and she does it flawlessly 💅

---

🌸 SYNOPSIS 🌸

datalad create-sibling-gitea [-h] [--dataset DATASET] [-r] [-R LEVELS]
       [-s NAME] [--existing {skip|error|reconfigure|replace}]
       [--api URL] [--credential NAME] [--access-protocol
       {https|ssh|https-ssh}] [--publish-depends SIBLINGNAME]
       [--private] [--description DESCRIPTION] [--dry-run] [--version]
       [<org-name>/]<repo-(base)name>

---

🦋 DESCRIPTION 🦋

so Gitea is this lightweight, free and open source code hosting solution and honestly? iconic. the whole point is that it has low resource demands, which means you can literally run it on inexpensive devices — like, yes, a Raspberry Pi 😭🧚 absolute main character behaviour.

this command uses the main Gitea instance at https://gitea.com as the default target, but no cap, you can point it at other deployments via the api parameter.

before you can use this command at all, you gotta generate a personal access token on the platform. the path is: Account->Settings->Applications->Generate Token. go do it, i'll wait 🫶

also! you can configure this command with datalad.create-sibling-ghlike.extra-remote-settings.NETLOC.KEY=VALUE so that any local KEY = VALUE configuration gets added to the sibling you just created, inside the local .git/config file. NETLOC is the domain of the Gitea instance you want that configuration to apply to. the result is behaviour equivalent to calling datalad's siblings('configure', ...)||siblings configure command with the respective KEY-VALUE pair after creating the sibling. and because this configuration, like any other, could be set at user- or system level, users do not need to add it to every sibling created with the service at NETLOC themselves. slay, efficiency. ✨

🎀 New in version 0.16 — she's not new new, but she's a classic for a reason.

---

👑 OPTIONS 👑

🎀 the positional argument

• [<org-name>/]<repo-(base)name> — the repository name, and optionally you can slap an '<organization>/' prefix on the front if the repository shall not reside under a user's namespace. when operating recursively, a suffix gets appended to this name for each subdataset. Constraints: value must be a string.

🧚 the flags

• -h, --help, --help-np — show this help message. --help-np forcefully disables the use of a pager for displaying the help message (so it just prints, no less-ing about it 💀).
• --dataset DATASET, -d DATASET — the dataset to create the publication target for. if you don't give it, an attempt is made to identify the dataset based on the current working directory (she'll sniff it out 🔥). Constraints: Value must be a Dataset or a valid identifier of a Dataset (e.g. a path) or value must be NONE.
• -r, --recursive — if set, recurse into potential subdatasets. go off, dig into the whole tree 🌈.
• -R LEVELS, --recursion-limit LEVELS — limit recursion into subdatasets to the given number of levels. Constraints: value must be convertible to type 'int' or value must be NONE.
• -s NAME, --name NAME — name of the sibling in the local dataset installation (the remote name, iykyk). Constraints: value must be a string or value must be NONE. [Default: 'gitea']
• --existing {skip|error|reconfigure|replace} — what to do when already-existing or already-configured siblings are discovered: skip the dataset ('skip'), update the configuration ('reconfigure'), or fail ('error').

💀 DEPRECATED DANGER ZONE: with 'replace', an existing repository will be irreversibly removed, re-initialized, and the sibling (re-)configured (thus it implies 'reconfigure'). REPLACE could lead to data loss! in interactive sessions a confirmation prompt is shown; an exception is raised in non-interactive sessions. the 'replace' mode will be removed in a future release. like… do not play with her 🙈

Constraints: value must be one of ('skip', 'error', 'reconfigure', 'replace'). [Default: 'error']

• --api URL — URL of the Gitea instance, without a 'api/<version>' suffix. Constraints: value must be a string or value must be NONE. [Default: 'https://gitea.com']
• --credential NAME — name of the credential providing a personal access token to be used for authorization. the token can be supplied via configuration setting 'datalad.credential.<name>.token', or environment variable DATALAD_CREDENTIAL_<NAME>_TOKEN, or will be queried from the active credential store using the provided name. if none is provided, the host-part of the API URL is used as a name (e.g. 'https://api.github.com' -> 'api.github.com'). Constraints: value must be a string or value must be NONE.
• --access-protocol {https|ssh|https-ssh} — access protocol/URL to configure for the sibling. with 'https-ssh', SSH is used for write access, whereas HTTPS is used for read access (best of both worlds, we love a hybrid 🦋). Constraints: value must be one of ('https', 'ssh', 'https-ssh'). [Default: 'https']
• --publish-depends SIBLINGNAME — add a dependency such that the given existing sibling is always published prior to the new sibling. this equals setting a configuration item 'remote.SIBLINGNAME.datalad-publish-depends'. this option can be given more than once to configure multiple dependencies. Constraints: value must be a string or value must be NONE.
• --private — if set, create a private repository 🔒 (your business, nobody else's).
• --description DESCRIPTION — brief description, displayed on the project's page. Constraints: value must be a string or value must be NONE.
• --dry-run — if set, no repository will be created. only tests for sibling name collisions will be performed, and would-be repository names are reported for all relevant datasets. a little peek before the real thing, we stan a cautious queen 👑.
• --version — show the module and its version which provides the command.

---

💜 AUTHORS 💜

datalad is developed by The DataLad Team and Contributors <team@datalad.org>. legends, every single one 🫶

---

and that's the whole page, bestie! 🌟 you're now fully certified in datalad create-sibling-gitea — go forth and sibling-ify.

sign-off time 🎀: this was datalad create-sibling-gitea, version 1.1.5, dated 2025-06-15 — from the General Commands Manual, with love. mwah 💋