Your api is quite powerful to access al kinds of information in a git repository. But there is no way to access git-notes.

https://git-scm.com/docs/git-notes

we use git-notes to annotate commits without changing the commit itself. git log shows them along with the commit messages and gitea shows them in the web ui. But the api access is missing.

it would be nice to have access to git-note

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

Describe the feature or problem you'd like to solve
Issue boards have all the user-made columns, but are missing the automatically created, open and closed columns. There is even a TODO for that, so that should be added.

Propose a Solution

• Add Open column for all issues that are in open state and don't belong any other column
• Add Closed column for all closed issues.

#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

Scalafix commits are currently attributed in the Git history to the Scala Steward user although it only did the easy part of running the rule. The hard part of writing the rule is done by someone else who's currently not attributed in any way. Wouldn't it be nice if we append Co-authored-by attributions to the Scalafix commit if the rule author(s) opts into i

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.