-
Notifications
You must be signed in to change notification settings - Fork 792
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
[enhancement] 添加 GitHub 问题模板 #253
Conversation
Signed-off-by: Ce Gao <[email protected]>
PTAL @at15 @AlexaraWu |
|
||
**日志信息**: | ||
|
||
<!-- 请在 https://pastebin.ubuntu.com/ 中的 Content 处粘贴上 `thesis.log` 内全部内容, 并将生成的链接附在此处, 如 https://pastebin.ubuntu.com/26345571/ --> |
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.
这样的设定是为了防止 log 太长导致 issue 看起来很费力..
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.
这个可以国内正常访问么?
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.
可以, pastebin.com 不可以
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 虽然可能也需要英文版的 template ? ....
btw: PR template 是不是也要来一个
@at15 我觉得提 PR 已经值得鼓励了, 就别用模板为难别人了吧 |
英文模板可以再开 issue 去 track 吧, 我对有没有外国友人提 issue 持怀疑态度 |
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
也可以只贴 log 的 Error 那一小块吧,其实 log 前面大部分的都没用。
嗯, 不过一个新手用户很难判断哪些信息是必要的 |
我又想了一下,为什么不把这个 Issue 模版放在 Wiki 里呢?然后在 |
这是 github 的 feature: https://help.github.com/articles/creating-an-issue-template-for-your-repository/ 会在每次创建新 issue 时默认出现在内容框里 |
哦哦,是我孤陋寡闻了。:joy: |
学到了学到了 |
@gaocegege 这个模版文件只有在默认分支里才有效吧?要不要把 dev 设置成默认分支?master 仅做发布使用? |
这不好吧, 等我们发了新版本, 到了 master 分支就好了. 对于发布我的建议是利用 GitHub Release 功能来发布, 开发就在 master 分支去做, 删掉 dev 分支 #237 这里是我的一些看法. 如果 master 只做发布那就跟用 GitHub Release 功能差不多了 |
👌 SGTM |
Signed-off-by: Ce Gao <[email protected]>
Ref #232
Signed-off-by: Ce Gao [email protected]