On Thu, 02 Feb 2023 01:37:02 -0300, Leonardo Brás wrote:
[...]
>
> It looks like it can be done by "Running CI/CD for external repositories".
>
> I removed my previous repository and then imported perfbook again using the
> above mentioned mode. According to the man page, it will run CI for the project
> whenever a new push to the referenced repository happens.
>
> So it's just a matter of waiting a new commit getting push'ed to see if it will
> be working.
Hi Leonardo,
I noticed a minor glitch in the generated PDFs.
They don't have Git commit info in the title page and footer area of
pages.
I can't tell what went wrong, but expected autodate.tex should look like:
-----
\date{February 1, 2023 \\ Commit: \texttt{v2022.09.25a-81-g4327c1f3809e}}
\newcommand{\commityear}{2023}
\newcommand{\commitid}{v2022.09.25a-81-g4327c1f3809e}
\IfQqzBg{}{\setboolean{qqzbg}{false}}
% tcolorbox version: 5.1
\tcbsetforeverylayer{autoparskip}
-----
It is not kept in the artifact, so I'm just guessing.
I guess utilities/autodate.sh failed to see .git/ in the build directory
and generated the following based on the build date instead:
-----
\date{February 2, 2023 }
\newcommand{\commityear}{2023}
\newcommand{\commitid}{}
\IfQqzBg{}{\setboolean{qqzbg}{false}}
% tcolorbox version: 5.1
\tcbsetforeverylayer{autoparskip}
-----
Not a big deal, but can you look into this?
BTW, I just requested a permission for accessing your repo.
Thanks, Akira
>
> Best regards,
> Leo
