-
Notifications
You must be signed in to change notification settings - Fork 9
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
Problem with deploying binary files? #92
Comments
The line in run.ts |
I found that posting binary files to Gists via the HTTP API is not supported. The only workaround seems to be to use git: # https://gist.github.com/remarkablemark/feff40b0a522f0c41c4eff0b77ea1d47
# with ssh
git clone [email protected]:<hash>.git gist
# with https
git clone https://gist.github.com/<hash>.git gist
cp BINARY gist
cd gist
git add BINARY
git commit -m "Add BINARY"
git push origin master I will find a way to implement this in the next few days. |
I just released a new patch version, hopefully it will solve the problem :) |
I am still getting this message
|
I have released another patch version. This should be fixed now. |
I can't reproduce the error in your previous (deleted?) comment. Is it working properly now? |
Thanks. Upon closer look, the error in the previous comment (deleted) was due to exceeded quota in the gist repository. The PDF that was deployed by this action is around 15 MB in size and with frequent pushes to the repository and Latex builds the quota was reached. So, entirely unrelated to your code. I will check this later with a new gist and will report here. |
Next thing I found out is that |
Yes, it does work now, using the new binary option. Thanks a lot for implementing this. |
I am using this action to deploy a server-side built PDF to a gist. For some reason, the PDF deposited in the gist is different from the PDF that was built on the github server. The deposited PDF is about twice as large and corrupt. I have narrowed down the problem to the actual file transfer. Is it possible that this action is limited to ASCII files?
The text was updated successfully, but these errors were encountered: