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.

One common use case for project maintainers is to update a broken pull request which was made by someone else.

Hub should be able to help maintainers doing the following steps:

• grab a pull request
• update the pull request (rebase or other change)
• update the pull request (aka pushing it)

Description

Gitea should document this. It is noticeably missing here. It is not in the app.ini file either.

try.gitea.com has a login with GitHub button in the UI, so it should be possible.

Edit: I see it is possible via settings. This should be mentioned on the corresponding doc pages.

I would like to map my "meson.build" files to python syntax.
I've tried the following without success:

• -m=build:python
• -m=meson.build:python

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:

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

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

After tracking a new file with git-lfs inside a subdirectory,

$ cd subdir && git lfs track myFile

the .gitattribute file is created inside the subdir and all the git hooks scripts are copied to core.hooksPath. The problem is when you are using a relative path in core.hooksPath (ex: .githooks), because they are copied to the current subdirectory

$ ls subdir/
	.gitattribut

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.

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?)

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