-
Notifications
You must be signed in to change notification settings - Fork 598
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
Your .github/scripts/close-invalid-link.cjs
is broken
#5826
Comments
I ran this validation
It seems like whoever wrote this code thought, I am getting the markdown, and forever the line that will contain the URL is the 18, it's so wrong, that could be acceptable but if for any reason you have a bug in your code you will close that issue too, you aren't checking the error, and if you fail, you close an issue, and someone accepted that PR You have to know that you must read line by line until read the title, and then make something like Clarifying this point, could someone reopen, or whatever, opens the issue |
.github/scripts/close-invalid-link.cjs
is broken
Add Github issue template for SSML (because this is a bug but it does require any reproduction URL) |
You're completely right about this. It's an edge case and I've had trouble figuring out the best way to validate this line. Unfortunately it's not supported by current yaml. Perhaps the best way forward is just to move it up so that we always have it in a standard place (for now). |
I don't understand your assertions:
|
Same issue:
Hey, the policy to report issues in Google is so disgusting, it's mentally exhausting, a Google Team must be able to send reports to another Google Team, I mean, I am not a Google worker, I am forced to deal with it I am frustrated, I want to never send any issue again |
Hi @jefer94, as I have already described to you earlier and in #5833, you are right and I need to fix this - I haven't had time to do it this week. I have already marked this issue as a p1 and acknowledged it. However, I will be closing this one and opening another one in its stead because you are violating our code of conduct. You are right there is an issue and I will fix it - please remember there are humans behind this issue queue and we are doing our best :) |
@sofisl I am not saying that I'm frustrated about you. I'm frustrated about Google Policy, I wrote about that issue because it is related to this issue Addressing that I am "violating our code of conduct," I will split the mistake by each one because it seems like you are telling me that I did something related to hating someone or laughing about newbies About @sofisl
About Google
About me
Right now clarifying those points, @sofisl , do you think that is fear everything I had to go through? Nothing starts or ends in you, who is in charge of maintaining and enforcing the respect towards the client and beta tester? We are human beings too and we have been going through a nightmare because Google has been systematically disrespecting us I will leave all that happened to me, for everyone to judge if this is fair and maybe add a clause to our code of conduct about Google respecting our, because we are human beings #5822 (comment) I suppose that it's fair |
Please make sure you have searched for information in the following guides.
Documentation Request
Document this error properly #5824
I have:
What do you want?, a frontend to run the SSML having a frontend written by us?
The text was updated successfully, but these errors were encountered: