Switch to LFS-supporting blob API #414
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Thanks! |
Member
|
Shipped the change with v0.79.1. |
Contributor
Author
|
@kyoshino Maybe worth mentioning in the readme, supporting LFS for Gitea is an advantage over both Decap and Static CMS :) |
Member
|
Just updated the README! Looks like uploading to LFS was broken in Gitea 1.23, but it’s been fixed in 1.24 just in time for the Gitea support in Sveltia 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switch from the raw file API to the media file API (https://gitea.com/api/swagger#/repository/repoGetRawFileOrLFS) for Gitea backing, which also directly supports retrieving LFS files. This de-facto enables LFS support for Gitea blobs.
There doesn't seem to be a similar endpoint for GitHub API.