gitlab-ci

Would be faster if we can reuse the already downloaded one, this is specially good for not cloud runners.
We should download the wrapped runner once (GH or GL), install it in the system and make cml-runner to use it always.
If we are changing the SCM we should download the other wrapped runner.

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

Describe the feature or problem you'd like to solve
My team has its issue board not on a specific repo, but on a group above the repos, currently it seems that glab doesn't allow selecting issue boards on groups, only on repos, so I can't display our issue board.

Propose a Solution
Find issue boards from all parent groups for the repo that is the currently open folder in the terminal,

#197 took care of being able to use # at the start of a line, but I just noticed that there isn't a great user flow for editing an issue that already has markdown headings.

1. Create an issue with at least 1 heading
2. Edit the issue with lab issue edit [ID]
3. Make changes and save
4. The issue will now have its heading(s) stripped out

I'm not sure what the best course would be, but