Skip to content

Absolute path for setting.CustomConf - #2085

Merged
lunny merged 1 commit into
go-gitea:masterfrom
ethantkoenig:fix/custom_conf
Jul 1, 2017
Merged

Absolute path for setting.CustomConf#2085
lunny merged 1 commit into
go-gitea:masterfrom
ethantkoenig:fix/custom_conf

Conversation

@ethantkoenig

Copy link
Copy Markdown
Member

Ensure that setting.CustomConf is an absolute path, so that the commands in .ssh/authorized_keys do not contain relative paths.

@lunny lunny added this to the 1.2.0 milestone Jun 30, 2017
@lunny lunny added the type/enhancement An improvement of existing functionality label Jun 30, 2017
@sapk

sapk commented Jun 30, 2017

Copy link
Copy Markdown
Member

LGTM

@tboerger tboerger added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jun 30, 2017
@lunny

lunny commented Jul 1, 2017

Copy link
Copy Markdown
Member

LGTM

@tboerger tboerger 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 Jul 1, 2017
@lunny
lunny merged commit 3c0705e into go-gitea:master Jul 1, 2017
@ethantkoenig
ethantkoenig deleted the fix/custom_conf branch July 5, 2017 02:38
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants