-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Add better template for issues #18737
base: main
Are you sure you want to change the base?
Add better template for issues #18737
Conversation
Signed-off-by: Vadim Bauer <[email protected]>
b40b992
to
9b3eaf9
Compare
--- | ||
<!-- | ||
Remember, an issue is not the place to ask questions. You can use [Stack Overflow](https://stackoverflow.com/questions/tagged/harbor) for that, or you may want to start a discussion in [Slack](https://cloud-native.slack.com/archives/CC1E09J6S). |
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.
Do we actually recommend users to use Stack Overflow? IMO, it would be more appropriate to simply state that Slack is the primary and recommended channel for support.
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.
as we do not monitor stack overflow I suggest we remove it
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.
or add that you can receive community help from there!
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.
updates?
This PR is being marked stale due to a period of inactivty. If this PR is still relevant, please comment or remove the stale label. Otherwise, this PR will close in 30 days. |
What do you @goharbor/all-maintainers think? Is it reasonable to have .github/ISSUE_TEMPLATE/bug_report.md and .github/ISSUE_TEMPLATE/issue.md at the same time? IMO, I would stick with only issues: |
This PR is being marked stale due to a period of inactivty. If this PR is still relevant, please comment or remove the stale label. Otherwise, this PR will close in 30 days. |
@Vad1mo will you remove the stackoverflow so we can merge this one :) |
Co-authored-by: Orlix <[email protected]> Signed-off-by: Vadim Bauer <[email protected]>
- [ ] https://tenforward.consulting/blog/how-to-write-a-good-bug-report | ||
--> | ||
|
||
# Problem Descriptions |
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.
Doesn't this part overlaps the content in "bug_report", if user wants to report a problem he/she should follow "bug_report.md" right?
- [ ] https://github.com/search?q=org%3Agoharbor+YOUR-ISSUE&type=issues | ||
- [ ] https://cloud-native.slack.com/archives/CC1E09J6S) | ||
- [ ] https://goharbor.io/docs/latest/ | ||
- [ ] https://tenforward.consulting/blog/how-to-write-a-good-bug-report |
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.
This link is not relevant
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.
The proposed change in the template has a lot overlap with "bug_report.md".
This PR will bring better template for new issues, to better guide users through the process of creating good and understandable issues.
Please indicate you've done the following: