From: "'Jan Ulrich Hasecke' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Include Git Hash in PDF
Date: Thu, 20 Jan 2022 15:45:43 +0100 [thread overview]
Message-ID: <98ea588d-45d4-1d50-5d30-c7d676728c23@mailbox.org> (raw)
Hi all,
I am lost.
How can I insert the commit hash from git in the output file?
I tried to evaluate "git rev-parse HEAD" in a build script and hand over
the result to the build process by setting a custom variable to the hash
string via --variable hash=${git rev-parse HEAD}. In my template I have
$hash$
I stored the hash in a file and tried to include it with -B, though this
would not be a good solution if it worked at all.
I guess this is quite a common requirement but I failed to find the
solution with Google & Co.
Any hints
juh
next reply other threads:[~2022-01-20 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 14:45 'Jan Ulrich Hasecke' via pandoc-discuss [this message]
[not found] ` <98ea588d-45d4-1d50-5d30-c7d676728c23-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2022-01-20 15:20 ` 'Saku Laesvuori' via pandoc-discuss
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98ea588d-45d4-1d50-5d30-c7d676728c23@mailbox.org \
--to=pandoc-discuss-/jypxa39uh5tlh3mbocffw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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 NNTP newsgroup(s).