I would like to switch between the dark/light theme more often during the day.

It would be awesome if the switch would be accessible more easily, e.g. in the menu bar.
Currently it is within the account settings and requires to hit a "save settings" button explicitly which is quite a long journey for a repetitive task.

Would be awesome if this feature would land! 🚀

This package could be used to enhance the readability of a lot of our tests:
https://github.com/JamieMason/expect-more/tree/master/packages/expect-more-jest/

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 just had this thought of having a GitHub action for glab.

**Do we need that? **

Yeah, I think we do.
Especially for repos on GitHub that are mirrored to GitLab. Maintainers may decide to accept issues and merge requests on GitHub, and write a script that automatically creates the issues and merge requests on GitLab too.
I think there are a lot of other use cases way beyond my imaginat

#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

Currently if you try to clone a repository from github and you don't have any ssh keys configured at github, you will fail to clone and get such message:

Fatal error: fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Even Permission denied (publickey). message is not shown.

@guyzmo offered to "suggest a

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.