Skip to content
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

github pages serving the reference file instead of the actual binary #1342

Closed
jspillers opened this issue Jul 1, 2016 · 15 comments
Closed

Comments

@jspillers
Copy link

jspillers commented Jul 1, 2016

I have a large file I am using git lfs to track as a part of a github.io repo. When I hit the URL to access the large file I am being served what I am assuming is the tiny reference file (134 bytes) instead of the large binary.

The file that should be the large file has the following contents:

version https://git-lfs.github.com/spec/v1
oid sha256:805400bc5ba8c96f8dff29a70c88d29c0566340b063e66f62326a1d3c3ea78ae
size 110517008

It's strange because this was just working... it wasn't until I committed a new version of the large file to the repo that I started getting this behavior. git lfs untrack + git rm and then re-adding the file appears to get it to push, but when I try to access it I get the wrong file.

The file in question is: http://www.stacktact.com/dynamic_terrain_objects_demo/Demo.unity3d

@technoweenie
Copy link
Contributor

GitHub Pages doesn't support Git LFS. This issue isn't really the place to discuss it (this repo is for the git-lfs client), but it is something I'd like to support.

@jspillers
Copy link
Author

Sorry for the noise, I will close this issue. For the future: where is the correct place to get support for git-lfs related issues that are not specific technical issues with the client?

@technoweenie
Copy link
Contributor

Depends on the issue. Since you're asking about GitHub Pages, you'll want to hit up GitHub Support: https://github.com/contact.

That said, I'll be forwarding this issue to the team, as a way to gauge interest in new features.

HybridDog added a commit to HybridDog/hairy-avenger that referenced this issue Jul 17, 2016
M  .gitattributes
@maxnordlund
Copy link

I also would like this, and it seems like this was already mentioned in #791. On a more technical level, what would be required to allow public read access to the blob tracked by git-lfs?

I assume that that is the blocker here, after that it's just a matter of writing a jekyll plugin that transforms some hrefs.

Going with that assumption, there needs to be another API that allows for creation of unauthenticated links to the blob in question. Probably a new transfer API type would be good here.

PS. While I do understand that you want to keep GitHub out of this repo, having people contact support removes the discussion, and subsequent answers, from the public. This makes it very hard to figure/find out why it doesn't work. If there is another place where a public discussion should take place, please let us know. Anyway, just some thoughts. DS.

@thom4parisot
Copy link

I'd be interested to give some feedback or use cases about this feature – I currently include video files for a book written with Asciidoc, published on GitHub Pages as HTML pages amongst others.

Cf. thom4parisot/nodebook@6273c01

@julianschiavo
Copy link

Any updates?

@bhaskarvk
Copy link

+1 this could really help a lot of use cases.

@harpojaeger
Copy link

Adding my +1 to the mix too!

@kyledewey
Copy link

Another +1 here!

@IoriBranford
Copy link

IoriBranford commented Oct 2, 2017

Workaround: Commit and push LFS files first. Then link to LFS files according to this format:

https://github.com/USER/PROJ/raw/BRANCH/FILEPATH

@bryanhanson
Copy link

bryanhanson commented Oct 4, 2017

The workaround mentioned by @loriBranford didn't work for me, but this did:

https://github.com/USER/PROJECT/blob/gh-pages/PATH_TO_FILE?raw=true

I can't claim any great insight here, this is the path associated with the view raw link when you are in the repo looking at the file you want to access. Entering this URL in a browser generates the download file dialog box, and I was able to successfully automate a download and install in the R environment.

@royuttam
Copy link

royuttam commented Nov 6, 2017

Dear jspillers,
I faced the same problem. How did you overcome it?

@Akagilnc
Copy link

Akagilnc commented Feb 26, 2019

@royuttam

https://media.githubusercontent.com/media/_Username_/_Project_/_Branch_/_Path_to_file_

You should replace all the xxx things to your's
I tried it just now it worked fine for me

loic-fejoz pushed a commit to labcesi-strasbourg/labcesi-strasbourg.github.io that referenced this issue Mar 4, 2019
GitHub.io does not support LFS.
See git-lfs/git-lfs#1342
kayecandy added a commit to kayecandy/mcb-configurator that referenced this issue Jul 31, 2019
shasheene added a commit to shasheene/rescuezilla.github.io that referenced this issue Oct 27, 2019
Replaces Git LFS tracking of images and fonts with regular git tracking using
the approach suggested in [1], because GitHub Pages does not support Git LFS
files (as of writing).

Removing Git LFS entirely was selected over updating URLs to absolute GitHub
paths (as done in [2]) as it's simpler to manage going forward.

[1] git-lfs/git-lfs#3026 (comment) (not
    using the subsequent comment's '--renormalize' due to old Git version).

[2] git-lfs/git-lfs#1342 (comment)
@bartlettroscoe
Copy link

This is not really a git-lfs issue but a GitHub Pages implementation issue, right?

@bk2204
Copy link
Member

bk2204 commented Nov 8, 2019

Yes, it is. Talking to GitHub support is the best way to address this.

Since this isn't a Git LFS issue, I'm going to close this.

@bk2204 bk2204 closed this as completed Nov 8, 2019
fiskhandlarn added a commit to bronoverrattvik/bronoverrattvik.github.io that referenced this issue Nov 21, 2019
mristin added a commit to admin-shell-io/aasx-package-explorer that referenced this issue Sep 10, 2020
GithHub Pages does not support Git LFS (see [this issue][1]). Since we
use *.jpg files only in the developer's documentation, the LFS tracking
is removed so that the files are properly served on GitHub Pages.

[1]: git-lfs/git-lfs#1342

The workflow build-test-inspect was intentionally skipped.
The workflow check-style was intentionally skipped.
The workflow check-release was intentionally skipped.
mristin added a commit to admin-shell-io/aasx-package-explorer that referenced this issue Sep 10, 2020
GithHub Pages does not support Git LFS (see [this issue][1]). Since we
use *.jpg files only in the developer's documentation, the LFS tracking
is removed so that the files are properly served on GitHub Pages.

[1]: git-lfs/git-lfs#1342

The workflow build-test-inspect was intentionally skipped.
The workflow check-style was intentionally skipped.
The workflow check-release was intentionally skipped.
mristin added a commit to admin-shell-io/aasx-package-explorer that referenced this issue Sep 10, 2020
GithHub Pages does not support Git LFS (see [this issue][1]). Since we
use *.jpg files only in the developer's documentation, the LFS tracking
is removed so that the files are properly served on GitHub Pages.

[1]: git-lfs/git-lfs#1342

The workflow build-test-inspect was intentionally skipped.
The workflow check-style was intentionally skipped.
The workflow check-release was intentionally skipped.
toolness added a commit to mysticsymbolic/apocalypse-animated-static-site that referenced this issue Oct 17, 2021
emranbm added a commit to qualiticcommunity/qualiticcommunity.github.io that referenced this issue Jan 30, 2022
Local relative link doesn't work with LFS, since GitHub pages doesn't
support git LFS.
Related issue: git-lfs/git-lfs#1342
littleali pushed a commit to qualiticcommunity/qualiticcommunity.github.io that referenced this issue Jan 30, 2022
Local relative link doesn't work with LFS, since GitHub pages doesn't
support git LFS.
Related issue: git-lfs/git-lfs#1342
kaliatech added a commit to kaliatech/depthkit-babylon-examples that referenced this issue Apr 5, 2022
lcd11001 added a commit to lcd11001/unity-city-builder that referenced this issue Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests