docs: Change feedback form to actionable questions
What kind of change does this PR introduce?
Improves the feedback form by adding actionable responses with options YES and NO rather than asking for a descriptive feedback.
Issue Number:
- Closes #805
Screenshots/videos:
Summary
built with Refined Cloudflare Pages Action
⚡ Cloudflare Pages Deployment
| Name | Status | Preview | Last Commit |
|---|---|---|---|
| website | ✅ Ready (View Log) | Visit Preview | c060079867e2fce0771ac77ae79a0b21e5de8c42 |
Hi @harshsbhat . The CI/CD workflow failed here: https://github.com/json-schema-org/website/actions/runs/10218752435/job/28275614951?pr=841 Can you please check it?
Also, the linked issue is tagged GSoD, so most probably it's part of an existing project board plan/epic. Please ensure that the work to be done is agreed upon and you are assigned the issue/ you have checked with the web team to work on an issue before creating a PR, as mentioned here
I am not very sure what is causing that error. Can you help me? I don't think it is from the file that I have edited
Also, the linked issue is tagged
GSoD, so most probably it's part of an existing project board plan/epic. Please ensure that the work to be done is agreed upon and you are assigned the issue/ you have checked with the web team to work on an issue before creating a PR, as mentioned here
Okay my bad. I won't start to work on something again without the APPROVAL/ASSIGNMENT for the same. So you want me to keep this PR or archive it?
Also, the linked issue is tagged
GSoD, so most probably it's part of an existing project board plan/epic. Please ensure that the work to be done is agreed upon and you are assigned the issue/ you have checked with the web team to work on an issue before creating a PR, as mentioned hereOkay my bad. I won't start to work on something again without the APPROVAL/ASSIGNMENT for the same. So you want me to keep this PR or archive it?
@DarhkVoyd
Also, the linked issue is tagged
GSoD, so most probably it's part of an existing project board plan/epic. Please ensure that the work to be done is agreed upon and you are assigned the issue/ you have checked with the web team to work on an issue before creating a PR, as mentioned hereOkay my bad. I won't start to work on something again without the APPROVAL/ASSIGNMENT for the same. So you want me to keep this PR or archive it?
No worries, Harsh. Let's keep this PR for now. Someone from the web team will review it and provide guidance on how to proceed.
I am not very sure what is causing that error. Can you help me? I don't think it is from the file that I have edited
Basically, the Codecov coverage token is not set up correctly, which is causing the job to fail. You don't need to do anything; the error is in the workflow configuration itself.
I am not very sure what is causing that error. Can you help me? I don't think it is from the file that I have edited
Basically, the Codecov coverage token is not set up correctly, which is causing the job to fail. You don't need to do anything; the error is in the workflow configuration itself.
Thanks a lot Alok for helping me out!
Hi everyone. After losing the Postman accounts we have lost access to the airtable used to store the data. Moving forward we decided to use google sheets instead and we still need to implement the change. Can we hold this change until we are able to store the data again?
@harshsbhat still available to work on this issue? We finally fixed the current feedback component to store data again so we can resume the work here and continue with the changes suggested on #762 . Happy to have a chat and work together on this.
@benjagm yeah sure. I will take a look at this tomorrow and ask some doubts if any. 😊
Hi, @harshsbhat it seems like tests are failing and some merge conflicts are there can you pls. fix them
Thanks for this contribution @harshsbhat . We are going to close this PR as there was no activity in the last 2 months.