-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Switch to non-deprecation setting #18358
Conversation
- Avoid by-default: `Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.18.0`
The |
Actually could we just migrate all of these LFS settings to (LFS_JWT_SECRET - might need to stay where it is though - I think that needs to migrate to |
Deprecate the current settings (like we do with |
I guess for the fallback deprecation probably needs to be for 1.19 removal. |
FYI: the Chinese config cheat sheet doesn't have a deprecation notice for the |
|
Hmm ... GitHub auto closed this one ..... nvm |
Codecov Report
@@ Coverage Diff @@
## main #18358 +/- ##
==========================================
+ Coverage 45.34% 46.06% +0.71%
==========================================
Files 841 840 -1
Lines 92860 92856 -4
==========================================
+ Hits 42108 42770 +662
+ Misses 44021 43301 -720
- Partials 6731 6785 +54
Continue to review full report at Codecov.
|
🚀 |
* 'main' of https://github.com/go-gitea/gitea: [skip ci] Updated translations via Crowdin Fix partial cloning a repo (go-gitea#18373) Switch to non-deprecation setting (go-gitea#18358) Update the SSH passthrough documentation (go-gitea#18366) Don't underline commit status icon on hover (go-gitea#18372)
* Switch to non-deprecation setting (Avoid by-default: "Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.18.0") * Update all references
[server]
LFS_CONTENT_PATH
present. Use[lfs]
PATH
instead. This fallback will be removed in v1.18.0"