gitlab

• Gitea version (or commit ref): 1.14.3 + 1.15-dev
• Database (use [x]):
  • MySQL
• Can you reproduce the bug at https://try.gitea.io:
  • Yes, https://try.gitea.io/org/will-leave-owners/teams/owners = no longer accessible for me
  • No

Description

A user on Codeberg reported perse accidentally left the "Owners" team

What would you like Renovate to be able to do?

Respect pinned versions and don't update them.
Here is a discussion where it all started: renovatebot/renovate#10970

In case of such setup:

  "devDependencies": {
    "packageA": "7.14.8",
    "packageB": "^7.14.5"
}

We would like renovate to respect pinned version of packageA and don't up

Many repositories need to fix, so please help if you like.

If you could help, it would be helpful if you could comment before starting the work not to overlapping.

Fix example

Run exit command after lint.

echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go

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

#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

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.

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

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