sanitizers / sanitizers/chronographer-github-app
[TODO] Improve towncrier check to support postfix number and extra suffices
Open
Nobody has claimed this yet.
bug
enhancement
good first issue
help wanted
- Dominant language
- Python
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
- https://github.com/tox-dev/tox/pull/1356#issuecomment-506258113
- https://github.com/hawkowl/towncrier/issues/153
Valid fragment examples:
docs/changelog/smth-else.deprecation(non-strict, not bound to an issue or a PR)docs/changelog/1355.misc(bound to an issue, it's implicit number is 0)docs/changelog/1355.bugfix.rst(bound to an issue, it's implicit number is 0, has a postfix and a suffix)docs/changelog/1355.bugfix.1.rst(bound to an issue, it's explicit number is 1, has a postfix and a suffix)docs/changelog/1355.feature.0.rst(bound to an issue, it's explicit number is 0, has a postfix and a suffix)docs/changelog/1355.feature.1.rst(bound to an issue, it's explicit number is 1, has a postfix and a suffix)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked tox-dev and towncrier discussions to understand the requested fragment syntax, then locate the repository's towncrier-check validation entry point. Use the listed valid examples to guide coverage for implicit or explicit postfix numbers and extra suffixes; done means all examples are accepted without regressing non-strict fragments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100