The feature to list commits from a subdirectory is already there but
so far the history link to it was missing. There is a History button
in the view_file.tmpl already so avoid showing two history buttons in
that case.
The GitHub webinterface has the same History button in the same place
so this makes gitea a little bit more compatible.
Signed-off-by: Bernhard Froehlich <decke@bluelife.at>
* Make reverse proxy auth optional
If the option ENABLE_REVERSE_PROXY_AUTHENTICATION is enabled, make
reverse proxy auth optional, instead of failing if the authentication
did not succeed.
Fixes#3973
Signed-off-by: Najib Idrissi <najib.idrissi.kaitouni@gmail.com>
* Update http.go
* Update "Upgrade from Gogs" en-us doc
- Move "Change gogs specific information" FROM/TO steps up
to just beneath matching section header, adjust indention
and explicitly specify syntax of code sample to provide
highlighting
- Adjust header levels to match what appears to be the
intended level, remove trailing decoration (see below)
- Move "Upgrading to most recent ..." section down, remove
decoration (section header formatting likely covers this
well enough already)
refs go-gitea/gitea#4286, go-gitea/gitea#3558
* Update "Upgrade from Gogs" fr-fr doc
- Adjust indention and explicitly specify syntax of code
sample to provide highlighting
- Adjust header levels to match what appears to be the
intended level, remove trailing decoration since
section header formatting likely covers this
well enough already
refs go-gitea/gitea#4286, go-gitea/gitea#3558
* Make sure author cannot reject/approve their own PR
* Disable buttons in templates too
* Remove unneccessary if check since the switch below catches it
* Fix IsOwner check
* Update template and remove new template variable
* Add alert template and redirect to diff page on review failure
* Redirect to files diff as a little update to #4632
* Add whitespace handling to PR-comparsion
In a PR we have to keep an eye on a lot of different things. But sometimes the
bare code is the key-thing we want to care about and just don't want to care
about fixed indention on some places. Especially if we follow the pathfinder
rule we face a lot of these situations because these changes don't break the
code in many languages but improve the readability a lot.
So this change introduce a fine graned button to adjust the way how the
reviewer want to see whitespace-changes within the code.
The possibilities reflect the possibilities from git itself except of the
`--ignore-blank-lines` flag because that one is also handled by `-b` and is
really rare.
Signed-off-by: Felix Nehrke <felix@nehrke.info>
* prevent pull request to be merged when PR is a WIP
* add tests
* add helper to prepend WIP: in PR title
* move default wip prefixes into settings
* use configurable WIP prefixes in javascript and default to first one in templates
* add documentation
* add unit test on pull model
Signed-off-by: Julien Tant <julien@craftyx.fr>
