Enable git LFS to not bloat the repo #248
Labels
No labels
type
dev tools
type
existing docs
type
new docs
good first issue
help wanted
needs
changes
needs
reporter feedback
needs
triage
needs
vote
role
engineering
role
fca
role
foa
role
fpl
role
initiative lead
role
mindshare
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
council/docs#248
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
While trying to fix some docs, I found that the repo, who contain just a bunch of text file is half a gigabit. The main reason is having a file that take around 20 to 50 time more space than all others, the brand book:
Could we not commit pdf files that impact so much the size of the repo and make checkout much longer, consume more resource, etc ?
Does Pagure support git LFS? I am not sure if it does. I don't recall when the brand book was added there, but in hindsight, we could have come up with a better location.
I think there has been some ongoing work to convert this document into a module in the Design Team docs, but I am not sure how far along that is.
Forgejo support git-lfs (I know gitea does), so this could be a conversion once there is a move.
One issue is whether Openshift support git-lfs.
I wasn't able to find a conclusive answer on whether this is supported or not after a quick web search (and a longer code search), so I will either have to test and/or ask someone with a deeper knowledge of Openshift in the office.
So answering to myself: https://github.com/openshift/library-go/blob/master/pkg/git/repository.go this is the code doing git operation on Openshift, no mention of git lfs. However, it should be on the image so I think the trick is just to do git lfs checkout manually before building, I guess somewhere in https://gitlab.com/fedora/docs/docs-website/docs-fp-o/-/blob/prod/build-scripts/rebuild-site.py?ref_type=heads
@misc I am looking to migrate this repository to Forgejo now. I am hitting a bug in the Pagure importer though. I will need to escalate for support.
I looked through another Forgejo repo I have admin access to on forge.fp.o and I did not see anything specific about git-lfs. Is this an extension or add-on we need for our version of Forgejo?
@misc wrote in #248 (comment):
Here we are, we made it to Forgejo. @misc, do you know if there is anything we need to do to get this working? Or is it on by default? Just wondering if there is action required, or if being here is enough for git-lfs to be enabled.