From: Rob Sargent <firstname.lastname@example.org>
To: Ken Mankoff <email@example.com>
Cc: Mark Barton <firstname.lastname@example.org>,
Tim Cross <email@example.com>,
Subject: Re: Org + git branches for derived files
Date: Sun, 15 Aug 2021 22:58:19 -0600 [thread overview]
Message-ID: <64438375-BAE6-4E51-A7D9-C2E9F949A38A@gmail.com> (raw)
> On Aug 15, 2021, at 7:02 PM, Ken Mankoff <firstname.lastname@example.org> wrote:
> Hi All,
> Thank you for the suggestions.
> I think the most elegant solution is to have a hook on GitHub that compiles the PDF on a remote server. But it takes a lot more work, because I don't necessarily have *everything* in Git - my local 'library.bib' usually isn't included, nor my custom emacs config, latexmkrc, etc.
> I'd just like the compiled PDF easily readable by anyone, but I don't want 100s of historical copies.
> There are a few solutions.
> 1) Maintain a branch with the 'no-history' files. When they need to be updated, commit and amend, then force-push. See https://stackoverflow.com/questions/22824922/git-commit-and-push-a-binary-file-but-dont-keep-history
> 2) Add the 'no-history' files to their own commit in the main branch. When they need to be updated, make a new commit and rebase/fixup from the previous commit. See https://stackoverflow.com/questions/12964145/how-to-config-git-to-overwrite-non-text-file-instead-of-version-controlled-it
Just to be clear, one is not required to use automated tools to generate the artifacts. They may be added manually. However, they are not typically retained forever so your own separate report may better suit your needs.
next prev parent reply other threads:[~2021-08-16 4:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 18:40 Org + git branches for derived files Ken Mankoff
2021-08-13 20:53 ` Juan Manuel Macías
2021-08-13 23:10 ` Tim Cross
2021-08-14 0:53 ` Mark Barton
2021-08-14 1:53 ` Rob Sargent
2021-08-14 3:44 ` Rob Sargent
2021-08-14 4:21 ` Samuel Wales
2021-08-16 1:02 ` Ken Mankoff
2021-08-16 4:58 ` Rob Sargent [this message]
2021-08-31 12:21 ` Timothy
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).