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

Flesh out the issue template to be much more detailed #4849

Merged
merged 2 commits into from May 12, 2016
Merged

Flesh out the issue template to be much more detailed #4849

merged 2 commits into from May 12, 2016

Conversation

envygeeks
Copy link
Contributor

This makes the issue template more robust, making check boxes so users can submit and check or check as they go. It also starts using HTML comments so that directions for the users aren't always displayed to us (gotta love Markdown.) And provides the users with more hints on what we would like from them when filing a ticket.

This makes the issue template more robust, making check boxes so users can submit and check or check as they go.  It also starts using HTML comments so that directions for the users aren't always displayed to us (gotta love Markdown.) And provides the users with more hints on what we would like from them when filing a ticket.
@envygeeks
Copy link
Contributor Author

An example of the final result can be seen here: https://github.com/envygeeks/jekyll/issues/1


- [ ] I believe this to be a bug, not a question about using Jekyll.
- [ ] I Read the CONTRIBUTION file at https://github.com/jekyll/jekyll/blob/master/.github/CONTRIBUTING.markdown
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be I read the contributing documentation at https://jekyllrb.com/docs/contributing/, right?

@parkr
Copy link
Member

parkr commented Apr 27, 2016

I like this! I think we should add back the section about what they expected to get. Maybe The Output I Wanted.

@parkr parkr added the meta label Apr 27, 2016
- [ ] I am on ***Fedora*** GNU/Linux
- [ ] I am on ***Arch*** GNU/Linux
- [ ] I am on ***Other*** GNU/Linux
- [ ] I am on ***Windows*** 10+
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why only Windows 10+? Because of upcoming bash support?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DirtyF Because Ruby already has shoddy Windows support, the last thing I want to do is exacerbate our support for it by supporting what we already have iffy support for by supporting a larger array of Windows versions.

* Link to jekyllrb.com as @parkr suggested.
* Add a few more directions and hints for Github Pages users who have errors.
* Add words that were missing and made stuff make no sense.
@envygeeks
Copy link
Contributor Author

Ping: @parkr @benbalter @alfredxing @jekyll/documentation @jekyll/ecosystem
This pull is completed, you can see an example: https://github.com/envygeeks/jekyll/issues/1
Please review for merge.

@parkr
Copy link
Member

parkr commented Apr 29, 2016

@envygeeks No where in the example does it explain the bug. It just has "What I Wanted," not "What I Got Instead"

@parkr parkr changed the title Make the issue template more robust. Flesh out the issue template to be much more detailed May 12, 2016
@parkr
Copy link
Member

parkr commented May 12, 2016

A little concerned this will be too much and folks won't read it but let's give it a shot.

@jekyllbot: merge +dev

@jekyllbot jekyllbot merged commit 8c9492d into jekyll:master May 12, 2016
jekyllbot added a commit that referenced this pull request May 12, 2016
@parkr parkr removed the fix label May 12, 2016
@jekyll jekyll locked and limited conversation to collaborators Jul 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants