Redocly / Redocly/json-to-json-schema
Added Issue Templates
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Currently the repo has no issue templates like bug, feature request and many
Markdown templates often made it difficult to capture the whole context, by expecting the contributors to read the markup, uncomment lines and delete relevant context.
Issue forms beta was released for public repositories last month, as mentioned by GitHub on this blog. We would like to migrate the issue templates to YAML-based forms which are easy to fill up and maintain, helping us capture relevant context.
There is no issue templates in the project so i would like to work on the issue
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 by reading the linked GitHub issue forms beta announcement and inspect the repository structure to confirm that no issue templates exist. Create YAML-based forms for the requested bug and feature-reporting use cases, with the relevant context captured through form fields, then verify that the forms are available when opening a new issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100