gitlab-api

Description of the problem, including code/CLI snippet

Documentation is missing an example how to make use of project import parameters.
The Gitlab-API supports these parameters (name,file,path,overwrite)

Expected Behavior

It would be good to add an example to the documentation (if those parameters are supported)

Actual Behavior

Specifications

• python-gitlab versi

I was wondering if there is a way to deal with issues in a file-like approach. For example

$ glab issue view 123 >> tmp.md
$ xdg-open tmp.md
$ glab issue update 123 --file tmp.md

That is, download the issue to a temporary file, edit as needed, update isse using the modified file.

This would be handy also to clone issues or to use an issue as a template:

$ glab issue c

Reference: https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap

Currently when a user initiates (non-ci) minimization, the commit message is just "Added user script in coqbot.sh". It should be something like "Added user script from coq/coq#<ISSUE #> in coqbot.sh" and should ideally include a link to the particular comment in the body of the commit message.