Skip to content

Conversation

@CrossDark
Copy link
Contributor

@CrossDark CrossDark commented Oct 26, 2025

I am submitting

  • a new package
  • an update for a package

Description: Explain what the package does and why it's useful.

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.

@typst-package-check typst-package-check bot added the new A new package submission. label Oct 26, 2025
@elegaanz elegaanz self-assigned this Oct 28, 2025
Copy link
Member

@elegaanz elegaanz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For info, you don't have to make a new version and a new PR for every change you make, you can push new commits to the same branch, it will update the previous PR. Only once a version is accepted and published, you have to make a new one if you want to make changes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you replace this file with an actual preview of the template please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'deleted this file. It is not currently in my local project.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one too.

@CrossDark
Copy link
Contributor Author

For info, you don't have to make a new version and a new PR for every change you make, you can push new commits to the same branch, it will update the previous PR. Only once a version is accepted and published, you have to make a new one if you want to make changes.

I got it. However, I have already switched to the V0.3 branch. Therefore, I may also need a new pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new A new package submission.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants