view doc/libervia-cli/merge-request.rst @ 3922:0ff265725489

plugin XEP-0447: handle attachment and download: - plugin XEP-0447 can now be used in message attachments and to retrieve an attachment - plugin attach: `attachment` being processed is added to `extra` so the handler can inspect it - plugin attach: `size` is added to attachment - plugin download: a whole attachment dict is now used in `download` and `file_download`/`file_download_complete`. `download_uri` can be used as a shortcut when just a URI is used. In addition to URI scheme handler, whole attachment handlers can now be registered with `register_download_handler` - plugin XEP-0363: `file_http_upload` `XEP-0363_upload_size` triggers have been renamed to `XEP-0363_upload_pre_slot` and is now using a dict with arguments, allowing for the size but also the filename to be modified, which is necessary for encryption (filename may be hidden from URL this way). - plugin XEP-0446: fix wrong element name - plugin XEP-0447: source handler can now be registered (`url-data` is registered by default) - plugin XEP-0447: source parsing has been put in a separated `parse_sources_elt` method, as it may be useful to do it independently (notably with XEP-0448) - plugin XEP-0447: parse received message and complete attachments when suitable - plugin XEP-0447: can now be used with message attachments - plugin XEP-0447: can now be used with attachments download - renamed `options` arguments to `extra` for consistency - some style change (progressive move from legacy camelCase to PEP8 snake_case) - some typing rel 379
author Goffi <goffi@goffi.org>
date Thu, 06 Oct 2022 16:02:05 +0200
parents c80a0f864b5d
children 524856bd7b19
line wrap: on
line source

===============================================
merge-request: create and manage merge requests
===============================================

Merge-request are used to propose some modifications to a project. They are generic and
are made to be used with several backends, but only Mercurial is implemented so far.

To prepare a merge request with Mercurial, you just need to have a clone of the project,
and do your modifications (either directly, or in a bookmark, a branch, or a MQ patch).

set
===

Create and publish a merge request. Once the modification on the project are done, simply
run the command from the repository (or specify its path with ``-r PATH, --repository
PATH``). If the project has set metadata (it can be done with a magic string in README),
you don't have to specify any service or node, it will be set automatically (but you still
can specify them if needed).

You may associate one or more labels to your request using ``-l LABELS, --label LABELS``.

By default, a confirmation is requested before publishing the request, you can publish
without confirmation by using the ``-f, --force`` flag.

If you have already done a merge request and you just want to update it, check its id and
specify it with ``-i ITEM, --item ITEM``, this will override the previous request with the
new updated one.

examples
--------

Publish a merge request (to be executed from the repository of the project you have
modified)::

  $ li merge-request set

Update an existing merge request, which has the id ``123`` (to be executed from the
reposiroty of the project you have modified)::

  $ li merge-request set -i 123

Do a merge request for repository at path ``~/some_project``, specifying a label
indicating it's work in progress (WIP)::

  $ li merge-request set -r ~/some_project --label WIP


get
===

Get and print one or more merge requests. By default only some metadata are shown (without
the patches), but you can use ``--verbose, -v`` to show details.

examples
--------

Show some metadata of last 5 merge requests::

  $ li merge-request get -M 5

Display details for merge request with id 456::

  $ li merge-request get -v -i 456


import
======

Import a merge request into your project. You mainly have to be in the project repository
(or specify it using ``-r PATH, --repository PATH``) and to specify the id of the patch to
import (using ``-i ITEM, --item ITEM``). The behaviour depends of the type of the patch,
for Mercurial, the patch will be imported as `MQ`_ patch.

.. _MQ: https://www.mercurial-scm.org/wiki/MqExtension

example
-------

Import the merge request with id 321::

  $ li merge-request import -i 321