Skip to content

No labels!

There aren’t any labels for this repository quite yet.

1-bug 🐛
1-bug 🐛
Issue type: Bug report (something isn't working as expected)
1-discussion 🗪
1-discussion 🗪
Issue type: Decision that needs to be discussed
1-feature-request ✨
1-feature-request ✨
Issue type: Request for a desirable, nice-to-have feature
1-question ❓
1-question ❓
Issue type: General or specific question about LTeX
2-confirmed
2-confirmed
Issue status: Confirmed, reproducible bug in LTeX
2-needs-info
2-needs-info
Issue status: We need more information (usually) from the submitter before continuing
2-unconfirmed
2-unconfirmed
Issue status: Bug that needs to be reproduced (all new bugs have this label)
2-upstream
2-upstream
Issue status: Bug is caused by some dependency, might have to wait before continuing
3-duplicate
3-duplicate
Issue resolution: Issue has been submitted before
3-fixed
3-fixed
Issue resolution: Issue has been fixed on the develop branch
3-invalid
3-invalid
Issue resolution: Issue does not follow template or is spam
3-no-action
3-no-action
Issue resolution: No action taken (e.g., question has been answered, issue has been withdrawn)
3-not-a-bug
3-not-a-bug
Issue resolution: LTeX behaves as expected, or bug cannot be reproduced
3-not-our-issue
3-not-our-issue
Issue resolution: This issue cannot be solved in LTeX, but in some dependency
3-out-of-scope
3-out-of-scope
Issue resolution: Issue is out of LTeX's feature scope, or fixing this would be too complicated
3-stale
3-stale
Issue resolution: Issue has been stale for too long
pr-dependabot 🤖
pr-dependabot 🤖
Pull request: Dependency update by Dependabot