lfs: do not require auth for public repositories
All threads resolved!
All threads resolved!
What does this MR do?
Allow LFS objects on public repos to be downloaded without authentication.
Are there points in the code the reviewer needs to double check?
Maybe?
Why was this MR needed?
LFS downloads on public repositories is obnoxious without this.
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Merge request reports
Activity
added 1 commit
- 21f09442 - lfs: do not require auth for public repositories
mentioned in issue #23360 (closed)
- Resolved by username-removed-152826
added 1 commit
- 6df7e2e0 - lfs: do not require auth for public repositories
added 1 commit
- e943e9b3 - lfs: do not require auth for public repositories
Ping? @stanhu Can you interpret the test results for me?
assigned to @rymai
added ~164274 lfs labels
- Resolved by username-removed-152826
@ben.boeckel Thanks, I had one remark, LGTM otherwise!
assigned to @ben.boeckel
added 1 commit
- 5c20e50f - lfs: do not require auth for public repositories
@ben.boeckel Awesome work, thanks a lot!
changed milestone to %8.17
assigned to @rymai
mentioned in commit 1a1381a4
Please register or sign in to reply