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.

Sign up for GitHub

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

Jump to bottom

Issue and pull request templates for all repos 🙀 #1652

Open
1 of 34 tasks
mischah opened this issue Nov 24, 2016 · 9 comments · May be fixed by yeoman/.github#9
Open
1 of 34 tasks

Issue and pull request templates for all repos 🙀 #1652

mischah opened this issue Nov 24, 2016 · 9 comments · May be fixed by yeoman/.github#9
Labels
easy enhancement meta to-confirm

Comments

@mischah
Copy link
Member

mischah commented Nov 24, 2016 •
edited
Loading

Hej,

after triaging just a few issues today I wish people would leave at least info about their OS, Node version and npm version.

I’m not sure, but I hope that explicitly asking for that in an issue template could help to prevent asking the same questions again and again.

So what do you thing about providing an issue and a PR template?

To reduce clutter in the project root we should store the Github »meta data« in a subdirectory as described here:

.github
├── CONTRIBUTING.md
├── ISSUE_TEMPLATE.md
└── PULL_REQUEST_TEMPLATE.md

To Do
@mischah
Copy link
Member Author

mischah commented Nov 28, 2016 •
edited
Loading

Thanks for the 👍 so far.
I’d like to make that to an actionable asap.

So let me know if you have any feedback to the drafts. Because I’m not a native english speaker 😗

@SBoudrias
Copy link
Member

Maybe open a PR, it'll be easier to comments lines.

Things I found out through lots of triaging. Most reporter don't know how to find what version of things they use.

mischah added a commit to yeoman/yo that referenced this issue Nov 28, 2016
@mischah
Add issue and pull request template
a506bf0 
… and move contributing.md to .github directory as well.
Related to yeoman/yeoman#1652
@mischah mischah mentioned this issue Nov 28, 2016
Merged
@mischah
Copy link
Member Author

mischah commented Nov 29, 2016

Removed drafts of templates since I openend yeoman/yo#492

@gruppjo gruppjo mentioned this issue Nov 30, 2016
Closed
@mischah mischah mentioned this issue Dec 1, 2016
Open
3 tasks
mischah added a commit to yeoman/yo that referenced this issue Dec 2, 2016
@mischah
Add issue and pull request template (#492)
e4a635c 
* Add issue and pull request template

… and move contributing.md to .github directory as well.
Related to yeoman/yeoman#1652

* Add info about getting versions

* Improvements suggested by Sindre

* Github → GitHub

* Move instructions about how to get versions

* Remove comment about how to handle GFM checkboxes
@mischah
Copy link
Member Author

mischah commented Dec 2, 2016

yo now has an issue an PR template sind yeoman/yo#492 landed 🎉

Let's see how those templates do, then we can consider moving them to other repos as well.

@UlisesGascon
Copy link
Member

@mischah do we want to promote the templates to the other repos? Are we happy with the current templates or do we want to iterate them?

@mischah
Copy link
Member Author

mischah commented Apr 5, 2022 •
edited
Loading

Hej @UlisesGascon, thanks for reaching out :octocat:

do we want to promote the templates to the other repos? Are we happy with the current templates or do we want to iterate them?

I am pretty much inactive in the whole Open Source Contributing Game for quite a while 🙈

But I just had a look at the most recent issues filed in /yeoman/yo/issues
And I would say the provided information regarding the environment are pretty useful and it would be worth the spread the templates over the other repos.

I’m just not quite sure if it feels okay to point to the gitter rooms for general questions 🤔 … (See /yeoman/yo/ISSUE_TEMPLATE.md) because the lack of activity over there.

Your thoughts about it? 💭

@UlisesGascon
Copy link
Member

I agree @mischah! We can spread the templates over the other repos. Regarding communications maybe we can create dedicated channel in Nodejs Slack community to centralize and open a bit more the communications with the community 🤔

@JoshuaKGoldberg JoshuaKGoldberg self-assigned this Jan 21, 2025
@JoshuaKGoldberg
Copy link

Coming back to this, I think it's definitely in scope of what #1779 is suggesting. Adding to the Maintenance Reboot Project.

@JoshuaKGoldberg JoshuaKGoldberg removed their assignment Jan 21, 2025
@UlisesGascon
Copy link
Member

PR in the oven that closes this (IMO) yeoman/.github#9 👍

@UlisesGascon UlisesGascon linked a pull request Jan 21, 2025 that will close this issue
Open
@JoshuaKGoldberg JoshuaKGoldberg moved this to In Progress in Maintenance Reboot Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
easy enhancement meta to-confirm
Projects
Maintenance Reboot
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Improve governance yeoman/.github
5 participants
@mischah @SBoudrias @JoshuaKGoldberg @UlisesGascon and others