-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix issue template - simplified version #6728
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
Conversation
6a2d661
to
a7903a8
Compare
Lots of issues filed didnt take the time to remove the boilerplate text and give the details needed. This format mimics the update to pull requests but inverts type and description.
Add same notes about the list of available issue types
a7903a8
to
7c9aa63
Compare
.github/issue_template.md
Outdated
- What toolchain is being used? | ||
- What is the SHA of Mbed OS (git log -n1 --oneline)? | ||
- Steps to reproduce (Did you publish code or a test case that exhibits the problem) | ||
--> | ||
### Description |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency with the PR template, Description should come first at the top ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'm actually fine as-is. Issues tend to need a lot more detail than PRs. Knowing the type of issue before the description helps frame the mindset before reading the description.
Who knows, maybe the PR template could be modified to have the type come before the description?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Open for suggestions, could also move PR type first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really seeing an issue with the original template, or a need to align particularly. PRs and issues are different things. Maybe change some things to checkboxes for a stylistic alignment, but structually this has always seemed fine to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lot of people ignore it (either remove it or provide default values). Similar what we experienced with PR template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I would like to have this resolved asap to start using simplified template in the issues. @AnotherButler Please review |
/morph build |
Build : SUCCESSBuild number : 1871 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1518 |
Test : SUCCESSBuild number : 1682 |
@AnotherButler Please review |
Make minor copy edits for grammar.
It was updated, time to review again ! |
.github/issue_template.md
Outdated
- What toolchain are you using? | ||
- What is the SHA of Mbed OS (git log -n1 --oneline)? | ||
- Steps to reproduce. (Did you publish code or a test case that exhibits the problem?) | ||
--> | ||
### Description |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: I would put description at the top, otherwise most people just delete the whole thing thinking it's just going to get in the way.
A lot of tools, like the auto-pr-thingy, just concatenate the description smack dab on top of the template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor tweak suggested
.github/issue_template.md
Outdated
Good example: https://os.mbed.com/docs/latest/reference/workflow.html | ||
Things to consider sharing: | ||
- What target does this relate to? | ||
- What toolchain are you using? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe tweak to say:
- What tools and their versions are being used?
- Which compiler and version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated via a new commit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/morph build |
Build : SUCCESSBuild number : 1900 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1547 |
Test : SUCCESSBuild number : 1718 |
Description
Cherry-picked from @sg in #6687. Plus updated to match the PR type description.
Pull request type