bookcls:0.1.0

[maucejo]

I am submitting

• a new package
• an update for a package

Description: The bookcls template is a Typst package designed for writing academic documents such as theses, French habilitations, or scientific books. It provides a structured format that adheres to academic standards, making it easier for authors to focus on content rather than formatting. This package provides three themes, several environments (front-matter, main-matter, appendix, back-matter) as well as several helper functions.

I have read and followed the submission guidelines and, in particular, I

• selected a name that isn't the most obvious or canonical name for what the package does
• added a typst.toml file with all required keys
• added a README.md with documentation for my package
• have chosen a license and added a LICENSE file or linked one in my README.md
• tested my package locally on my system and it worked
• excluded PDFs or README images, if any, but not the LICENSE
• ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

[elegaanz]

I'm not sure what happened with the Git history here, but could you make sure to only include changes to the new package, and not touch your other packages please?

[maucejo]

Actually, I didn't touch my other packages when I submitted my new package. After the observing the error, I removed the manual.pdf files from my forked repository, since it seems to be the cause of the errors.

[elegaanz]

I think you need to re-introduce the PDF files (by resetting your branch to a previous commit ideally) and then sync your fork. I can provide more detailed explanation on how to do that if needed.

[maucejo]

Ana, thank you for your offer. I indeed need some help to revert to a previous commit.
My main problem is that I work on my fork of Typst packages on the Github website only (due to the size of the packages repo). So I can't write git reset --hard <hash of the commit>. I think it would be better to revert to the commit 4699023 and it seems we can't revert directly in the website...