docs: Customize GitHub issue templates #16
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oliver-pham
requested review from
hlavu,
tuanthanh2067,
minhhang107 and
mqnguyen5
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/tuanthanh2067/seeksi/57dEeSPEPEXyg22epjum7KfCh7KV |
tuanthanh2067
approved these changes
Jan 14, 2022
|
Yeah, no due date is necessary in my opinion. Feel free to merge this PR! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #8
This PR should should refine our issue templates for feature request & bug report.
I'm still considering adding a due date to the issue templates, but it may be unnecessary. Because our issues are divided and tackled in sprints, we may not need to worry too much about an exact due date. As long as we complete them by the end of a sprint, it should be ok, right?