Many papers are archived in Arxiv.org. A lot of them might also have version histories. But it seems we can't get the update information for one paper when it is updated. Does github support the version history for pdf files? Maybe github can provide the version control for Arxiv.org.
Does GitHub support the version history for pdf files?
Not directly, in that it cannot display diff.
You would need an external diff like diffpdf for that.
Maybe github can provide the version control for Arxiv.org.
Right now, GitHub is not used by Arxiv.org. Their "new" page mentions in 2008:
We have implemented version control for papers submitted prior to November 1997 in the same way as for papers submitted later.
In 2011:
Bulk data available on Amazon S3: The bulk data available for download from Amazon S3 has been extended to include both PDF and source files of the latest versions of all arXiv articles.
Related
I see people hosting files (usually binary files) under https://github.com/downloads/<user>/<repository>/. How do they do it?
You can't. That doesn't exist anymore... GitHub used to have a Downloads API that was replaced by the Releases API back in 2013. Old links were redirected and still work as you can see on the example you provided in the comments.
Nowadays, if you want to make files available for download, you should use either the Releases feature or the Packages feature.
Does anyone know what is the difference between a GitHub release and the actual release that software company announces?
I'm trying to find the different versions of vue.js, on the vue.js official website there are only two versions but on the GitHub repository many releases I was wondered if the two concepts are different?
Release(may be downloadable link) version is just file which is uploaded.
Just they decide to provide only two version(may be latest) on official site.
It is all. If same version, (should be) same file. It is just like top selling tag on a store.
When they release a GitHub version, it is supposed to be open source. The one the company releases may have more code they have not reeased yet or is confidential.
We are using Pentaho Report Designer (PRD) to build out some PDFs and Excel files to the customer. Does anyone have a good strategy for doing version control on these reports? The prpt files seem to be a zipped set of xml. Is there a better format so we can tell what changed from one commit to another?
It is a pain. That's the only format.
You can get pre to work with unzipped archives I believe. But the only way you're going to get nice version control is to unzip before you commit. And re zip on checkout or update.
When I inquire that from Pentaho support for my purposes they said such feature is not there to maintain the version of PRD reports. Then they raised a JIRA request as a new feature.
JIRA ticket
In your commit comment, plainly state what was changed. You won't be able to do a diff on it to see the changes, but by looking at the commits on it you can see what was changed, who made the change, and when.
How can I easily backup & restore bugtracker of project on Github? Repository itself is obvious, wiki is also a git repository - but what about bugtracker?
I want to fully backup bugtracker (tickets, attached imaged, labels, comments, images attached in comments, dates of creation and closing of tickets etc) with ability to recreate it on github account.
Saving it as editable format would be a good bonus.
I am aware about Github API and that I can make tool like this. But I would prefer to use (optionally improve) existing one.
Existing ones mainly export the issue text, not always their attachments.
github-issues-export
github-to-bitbucket-issues-migration
Those services could be extended with the issue API to export more.
A more complete service is backhub.co, which exports a bit more (but isn't as easily expendable). It is free for public repos.
Update August 2018: vorburger adds in the comments a direct link example of how to use the GitHub Issues API to obtain all comments from a particular issue:
https://api.github.com/repos/JDKMissionControl/jmc/issues/1/comments
I'd like to see a graph of the total size of a repo over time.
(this is useful as it can help to see if poeple are accidentally checking in stuff they shouldn't, like binaries etc.)
The standard github graphs show lots of interesting stuff, but not this simple metric so far as I can see.
Any ideas?
Have you considered giving a try to the GitHub Archive project?
As stated on the home page
GitHub Archive is a project to record the public GitHub timeline, archive it, and make it easily accessible for further analysis.
GitHub Archive provides downloadable json datasets and also makes its content available via Google BigQuery for easy online analysis (see this document for more information on this topic and sample queries).
Note: GitHub timeline data is available starting February 12, 2011.
Update:
Provided your repository is private, you may have to fallback to the GitHub API and consider the size member. In order to graph, you'd have to trigger a regularly call to the API and locally store the result.
syntax: /repos/:user/:repo [GET]
example: https://api.github.com/repos/libgit2/libgit2