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

merge github-issue-guide with the issue template #4636

Merged
merged 4 commits into from
Dec 6, 2018
Merged

merge github-issue-guide with the issue template #4636

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ab33445
merge github-issue-guide with the issue template
Stebalien Feb 1, 2018
d0789c7
add comment about reading github's issues guide to the issue template
Stebalien Feb 1, 2018
3099f2f
add panic issue type to issue template
Stebalien Feb 1, 2018
0a6c7c1
Re update issue description to be shorter and more actionable
momack2 Dec 6, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 18 additions & 3 deletions ISSUE_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,29 @@
<!-- 🔥❓If you have a *QUESTION* about IPFS, please ask on our forum at https://discuss.ipfs.io 🔥❓

The go-ipfs issues are *only* for bug reports and directly actionable feature requests. Please direct all other questions, ideas, or suggestions to our discuss forum. Remember to search the issue tracker for an existing report concerning your issue before posting, and see https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue. -->
The go-ipfs issues are *only* for bug reports and directly actionable feature requests. Please direct all other questions, ideas, or suggestions to our discuss forum. Remember to search the issue tracker for an existing report concerning your issue before posting, and see https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue. If you want to discuss a design idea related to ipfs but not directly related to the go implementation, please file an issue at https://github.com/ipfs/ipfs.
-->

#### Version information:
<!-- Output From `ipfs version --all`

Please check dist.ipfs.io for a newer version of go-ipfs and update if necessary. Report back if the problem persists. -->
Please check dist.ipfs.io for a newer version of go-ipfs and update if necessary. Report back if the problem persists.

If you can't run `ipfs version --all` or that command fails, include as much information as you can: IPFS version, computer architecture (e.g., Intel x86 64bit), operating system, etc. -->

#### Type:
<!-- Bug, Feature, Enhancement, Etc -->
<!--

- "bug": If what you are filing is a bug.
- "panic": If you'd like to report an application panic, segfault, crash, etc.
Copy link
Contributor

Choose a reason for hiding this comment

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

I suppose that is a bit more specific than the original description of "If it is a severe bug.", but I think I would use this also when the server dies with an error message when responding to a (perhaps invalid) request from the client.

- "feature": If you'd like to suggest a feature.
- "enhancement ": If you'd like to suggest an improvement on to existing feature.
- "test failure": If the tests are failing
- "doc": If it's related to missing/incorrect documentation.
- "meta": If its a meta issue about this project/this repository/issue tracker.
Copy link
Contributor

Choose a reason for hiding this comment

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

You left out panic, I think that is useful for cases when ipfs crashes or other obvious bug. A panic in my view indicates a programmer error.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah. Good point. Delineates "I think this is a bug" and "this is definitely a bug".


Feel free to choose your own category if none of these fit your needs. However, be careful, that may indicate that your issue doesn't belong in this repo.

-->

#### Description:
<!-- This is where you get to tell us what went wrong or your specific feature request. When doing so, please make sure to include *all* relevant information.
Expand Down
87 changes: 0 additions & 87 deletions docs/github-issue-guide.md
View file
Open in desktop

This file was deleted.