Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an Issue template to automatically assigned the label tags when someone open an Issue #12748

Open
alancassis opened this issue Jul 22, 2024 · 2 comments
Assignees

Comments

@alancassis
Copy link

Refer to documentation:
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

When opening the issue the user will be asked about what this issue refers to, i.e.:

This issue is a(n): [ ] BUG, [ ] Crash, [ ] Feature Request, [ ] Improvement, [ ] Logic Error, etc

This issue apply to the architecture(s): [ ] All, [ ] ARM, [ ] ARM64, [ ] AVR, [ ] CEVA [ ] HC, [ ] MIPS, etc

What areas are this issue related to: [ ] Audio, [ ] Clock Control, [ ] Ethernet, [ ] GPIO, [ ] Memory, etc

Which vendors are affected: [ ] AMD, [ ] Atmel/Microchip [ ] Broadcom, [ ] Espressif, [ ] Renesas, [ ] STMicroelectronics, etc

@acassis acassis self-assigned this Jul 22, 2024
@simbit18
Copy link
Contributor

Here I have created three example templates
https://github.com/simbit18/nuttx-testing-templates/issues/new/choose

Bug report
Report a bug to improve NuttX stability

Feature request
Request an enhancement for NuttX

General Help
Get general support regarding NuttX

@acassis
Copy link
Contributor

acassis commented Jul 24, 2024

Really cool @simbit18 !!! Thank you very much for implementing it.

I think for affected architecture we cannot use Combo-box, because an issue can affect two or three architecture.

Also it is important that "Related area" area also be an automatic label/tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants