Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

the user should have an api to delete his own account

you just have to look at
https://github.com/go-gitea/gitea/blob/a7f0ce620774be861f11b57d426ab59e27e4171a/routers/api/v1/admin/user.go#L307-L320

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

It will be useful to install/show helm chart pre releases from a helm repo. Using helm from the commandline pre releases are also not shown or installed. Adding the --devel it will show or install pre releases. It would be nice to have a switch to show the pre releases or not like for example in rancher.
![rancher](https://user-images.githubusercontent.com/106823500/171875868-3c090565-2060-4fcc-a

The (still undocumented) feature is great for our purpose, but can you add the same functionality to the post-update hook (in the same manner, of course)?

I have added a script to the post-update to check the database-version. If they not match, the script returns exit 1. It would be great if the post-update hook could log a error- or warning-message, so the slack-notification gets a message (l

Add a network option in creating workload

like rancher‘s Networking tab

** During workload creation, user can customize own hosts and DNS search doma

Small feature request. I am using helmfile for the deployment of our k8s infrastructure and wanted to use sops for encryption of secrets. I need to use the --keyservice but as I am calling sops inside a wrapper (helmfile) of a wrapper (helm secrets) I cannot pass this variable to sops in a clean way.

Could you provide an alternative way to provide this option to sops in the .sops.conf and/or i

So much emphasis on the buttons is not needed.

Description

Currently we are using Semantic Pull Requests to check in PR but the project is no longer maintained. we need some alternatives.

e.g.

• https://github.com/amannn/action-semantic-pull-request

If anyone is interested in this, please submit a PR to complete this replacement

Description

Help increase external contributors by quantity & by quality & reduce