NASA-AMMOS / NASA-AMMOS/AIT-Core
Consistent templates for issue tickets and pull-requests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 56
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 3
Description
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
N/A
Describe the feature request
As part of the NASA-AMMOS/slim project, we've been developing standardized issue templates and pull request templates to make it easier for projects to read and write tickets / pull-requests in a more consistent way.
See our issue template examples for bugs and new features - pure Markdown versions also available. Please go here for further details.
See an example of our pull request templates here and further described here.
If this is helpful, let me know. We can push out a pull-request with these templates for your repository.
Sample bug report:
Sample feature request:
Sample pull-request:
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
Review the linked NASA-AMMOS/slim examples, including documentation/starter-kits/ISSUE_TEMPLATES/github/bug_report.yml, feature_request.yml, and PULL_REQUEST_TEMPLATE.md. Compare them with this repository's current contribution setup. Done means the repository has consistent issue and pull-request templates matching the agreed project needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100