Started on default port 3000, chose another port for both HTTP Port and Application URL. After pressing "Install Gogs" it redirected to the URL with the new port, but nobody listens there. It still listens on port 3000. I need to restart the app for the change of port to take effect.

Is there an example file to show the format this accepts?

I've tried a few different ways and I keep getting the whole file as the title.

• Gitea version (or commit ref): 1.9.3
• Git version: 2.23.0
• Operating system: Linux
• Database (use [x]):
  • [ x] PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • [ x] Not relevant
• Log gist:

Description

The configuration parameter "ALLOW_ONLY_EXTERNAL_REGISTRATION

As mentioned in @sharkdp's comment on issue #651, the order in which things show up in --help was intended to be "most useful"/"most frequently used" first.

As @sharkdp also pointed out in his comment, some of the entries need to be moved to bring --help back in line with its intended ordering scheme.

I'm opening this is

Is your feature request related to a problem? Please describe.
It would be cool if e.g. pressing 1 focused the status panel, 2 focused the files panel, etc.

Is your feature request related to a problem? Please describe.

I have the following field structure:

      - label: English
        name: en
        widget: object
        fields:
          - {label: Title , name: title, widget: string}
          - {label: Body, name: body, widget: markdown}
      - label: Spanish
        name: es
        widget: object
        fields:

Add some docs for the new metrics added in #7257.

New plugin motivation

In Azure DevOps semantic release has to be triggered via a normal bash command, also npm install must be run before, environment variables have to be set up...

In order to make semantic release work for a broader range of application, e.g. non-npm based and make use of service connection instead of environment variables it would be cool to have an Azure DevOps Pipeli

.gitattributes

tools.tgz filter=lfs diff=lfs merge=lfs -text

git status

On branch master
Your branch is ahead of 'kuvaldini/master' by 1 commit.
  (use "git push" to publish your local commits)

Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

        modified:   Dockerfile

Reproduction steps

Visit https://libgit2.org/libgit2/#HEAD. Look for git_repository_set_refdb. It is not present, nor are any of the functions I checked from include/git2/sys/repository.h.

Version of libgit2 (release number or SHA1)

Whatever the website is at as of Sep 6, 2019. (Perhaps the website should provide a sha indicating what HEAD is?)

There are a set of steps that would probably be useful in troubleshooting problems with Commitizen and Adapters. Over time it would be nice to have a place for them to be documented rather than being stuck in issues.

I think the work you've done on this is amazing. Seems like a great project, but your README is a bit bloated and hard to decipher. Might I suggest you condense it down into a set of readable chunks and maybe link off to the wiki for the more detailed bits.

Its only my opinion, but I find that answering the following questions, in order, helps to simplify docs.

• who? - who wrote the p