-
Notifications
You must be signed in to change notification settings - Fork 66
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
feat: introduce new design issue section #308
base: master
Are you sure you want to change the base?
feat: introduce new design issue section #308
Conversation
Changes: - add initial template for the design issue
@Mayaleeeee I've opened this PR. Please describe the fields which should be present in the issue template. |
Hello, @AnimeshKumar923. Thanks for the pinging. I will respond to this tomorrow with the details. |
Hey @AnimeshKumar923 thanks for all your hard work. I admire your patience and dedication. Below is how the Design Issue Report 🎨Issue Title: Describe the Issue: Expected Outcome: Screenshots: Steps to Reproduce:
Browser/Device: Additional Notes: Check Before Submitting:
Would you like to help fix this issue? (Not required, but appreciated!)
|
@Mayaleeeee I have fever right now. I'll take a look at it in few days. Thanks! |
Thank you @AnimeshKumar923 |
Changes: - update issue format according to the issue guideline provided here: asyncapi#308 (comment)
Hi @Mayaleeeee |
Thanks, @AnimeshKumar923 I have reviewed the changes, and everything looks good. The only adjustment I would like to request is to keep lines 66-67 as they appear in the screenshot below and not to use the text I provided for those lines. |
added suggestions from: asyncapi#308 (comment)
Hi @Mayaleeeee I've made the suggested changes through 70068d4, PTAL |
Looks good @AnimeshKumar923 |
Description
Related issue(s)
Resolves asyncapi/website#1721