Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always emit the configuration path #17036

Conversation

zeripath
Copy link
Contributor

Often when handling problems it is not clear which configuration file Gitea is
using. This PR simply ensures that the configuration file is emitted.

Signed-off-by: Andrew Thornton art27@cantab.net

Often when handling problems it is not clear which configuration file Gitea is
using. This PR simply ensures that the configuration file is emitted.

Signed-off-by: Andrew Thornton <art27@cantab.net>
@zeripath zeripath added this to the 1.16.0 milestone Sep 13, 2021
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Sep 13, 2021
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Sep 13, 2021
@axifive
Copy link
Member

axifive commented Sep 13, 2021

@delvh Your approvals isn't counted by the bot, just apply as a maintainer. @6543 wrote you before at discord

@techknowlogick techknowlogick merged commit 04b233e into go-gitea:main Sep 14, 2021
@zeripath zeripath deleted the ensure-we-always-emit-what-config-we-use branch September 14, 2021 06:56
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
@zeripath zeripath added the type/enhancement An improvement of existing functionality label Jan 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/enhancement An improvement of existing functionality type/miscellaneous
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants