Project: add GitHub issue templates (bug report, feature request)

Open Beginner friendly
  • Is something wrong?
#46 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github, javascript
Domain
developer-experience, documentation

Research direction

Read CONTRIBUTING.md and inspect the existing files under .github/ to match the repository's conventions. Add the three specified issue template files and the one-line mention in CONTRIBUTING.md; check that both forms appear in GitHub's New issue chooser and run npm test or npm run test:unit.

Written by the indexing model from the issue text.

Description

documentation good first issue help wanted project

Context
.github/ has a pull request template and workflows but no issue templates, so bug reports arrive without the version, OS or reproduction steps we need.

Proposed scope

  • .github/ISSUE_TEMPLATE/bug_report.yml (GitHub issue form): OrchestrAI version, OS, steps to reproduce, expected vs actual, logs or screenshot, checkbox "I searched existing issues".
  • .github/ISSUE_TEMPLATE/feature_request.yml: problem, proposed behavior, alternatives, area dropdown matching our area:* labels.
  • .github/ISSUE_TEMPLATE/config.yml: disable blank issues; add a contact link pointing security reports to private advisories.
  • Forms should apply the bug / enhancement labels automatically.

Acceptance criteria

  • The three files validate (GitHub's "New issue" chooser on your fork shows both forms).
  • CONTRIBUTING.md mentions the templates in one line.

How to get started

  1. Read CONTRIBUTING.md, run npm install && npm start.
  2. Comment here so nobody duplicates the work; ask questions in the thread, we are happy to point you at the right file.
  3. Open a PR that references this issue. Run npm test (or npm run test:unit) first.
Dominant language
JavaScript
Stars
0
Forks
0
Avg merge
1d 17h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from adaumsilva/OrchestrAI

All issues in adaumsilva/OrchestrAI

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.