You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/02/19 13:40:58 UTC
[GitHub] [apisix-website] navendu-pottekkat opened a new pull request #894: feat: add issue forms
navendu-pottekkat opened a new pull request #894:
URL: https://github.com/apache/apisix-website/pull/894
Signed-off-by: Navendu Pottekkat <na...@gmail.com>
Fixes: #890
Changes:
<!-- Add here what changes were made in this pull request and if possible provide links showcasing the changes. -->
Added issue templates for "Documentation Issue" and "Website Issue".
Screenshots of the change:
<!-- Add screenshots depicting the changes. -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] bzp2010 commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
bzp2010 commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046027159
Great step, maybe the content still needs to be tweaked, so let other contributors to take a look.
ping @juzhiyuan @Baoyuantop @guoqqqi
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
netlify[bot] commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046021152
👷 Deploy Preview for *apache-apisix* processing.
🔨 Explore the source changes: e794411396d126f369da96bed2a52d9a3cf67475
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6210f363038f360008e255b8](https://app.netlify.com/sites/apache-apisix/deploys/6210f363038f360008e255b8)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] navendu-pottekkat commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
navendu-pottekkat commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046164612
Yes. That was indeed my plan after this PR. We should consolidate the labels across all repos and make it semantic.
For example,
area/docs and area/website
issue/invalid and issue/duplicate etc
I will open up a new issue in the APISIX repo and create a document to track this and to arrive at a decision.
But meanwhile, we can merge this PR to have a template for now and later edit the labels once we have them.
What do you think @bzp2010 ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] yzeng25 merged pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
yzeng25 merged pull request #894:
URL: https://github.com/apache/apisix-website/pull/894
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046021152
✔️ Deploy Preview for *apache-apisix* canceled.
🔨 Explore the source changes: e794411396d126f369da96bed2a52d9a3cf67475
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6210f363038f360008e255b8](https://app.netlify.com/sites/apache-apisix/deploys/6210f363038f360008e255b8)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] navendu-pottekkat edited a comment on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
navendu-pottekkat edited a comment on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046164612
Yes. That was indeed my plan after this PR. We should consolidate the labels across all repos and make it semantic.
For example,
area/docs and area/website
issue/invalid and issue/duplicate etc
I will open up a new issue in the APISIX repo and create a document to track this and to arrive at a decision.
But meanwhile, we can merge this PR to have a template for now and later edit the labels once we have them.
What do you think @Baoyuantop ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] navendu-pottekkat commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
navendu-pottekkat commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046474284
Thanks all. As discussed, I will open up an issue and start a discussion to consolidate what labels we will use across Apache APISIX repos.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] Baoyuantop commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
Baoyuantop commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046128614
Hi @navendu-pottekkat, thanks. This is very friendly to other contributors, but the categories may need a little more consideration. For example, whether to consider `feat`、`bug`、`discuss`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] juzhiyuan commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046445469
> Do we need an original blank issue page for fallback? For example, if none of the templates fits an issue, but I still want to raise that issue via GitHub, how is that supposed to work?
Hi @yzeng25, please have a check on the screenshot 😄 It has an Open a blank issue link.
> How to categorize the existing issues by this PR (and potentially next PRs)? Or maybe we can leave them as they are right now?
I agree to leave them as right now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] yzeng25 commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
yzeng25 commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046447270
> > Do we need an original blank issue page for fallback? For example, if none of the templates fits an issue, but I still want to raise that issue via GitHub, how is that supposed to work?
>
> Hi @yzeng25, please have a check on the screenshot 😄 It has an Open a blank issue link.
>
> > How to categorize the existing issues by this PR (and potentially next PRs)? Or maybe we can leave them as they are right now?
>
> I agree to leave them as right now.
Oh OK, that's great. I thought deleting `.github/issue_template.md` would result in no fallback option. Thanks for clarification.
Then LGTM.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] navendu-pottekkat commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
navendu-pottekkat commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046030680
@bzp2010 Yes. Sure.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] yzeng25 commented on pull request #894: feat: add issue forms
Posted by GitBox <gi...@apache.org>.
yzeng25 commented on pull request #894:
URL: https://github.com/apache/apisix-website/pull/894#issuecomment-1046420219
Just out of curiosity, I have a couple questions:
1. Do we need an original blank issue page for fallback? For example, if none of the templates fits an issue, but I still want to raise that issue via GitHub, how is that supposed to work?
2. How to categorize the existing issues by this PR (and potentially next PRs)? Or maybe we can leave them as they are right now?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org