-
Notifications
You must be signed in to change notification settings - Fork 0
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
(Just having some fun!) I don't like your tone, friend #1
Comments
That label needs to be way more common |
#truth |
Actually did manage to find another use of the wontfix label 😆 and I have to say I agree with him. Don’t see any real gain to differentiating between js and jsx files. |
Yeah, I've seen I do believe it is actually one of GitHub's preloaded tags for an issue. |
Ah, that would make sense. I think the reason I like it so much is the phrasing. I understand its meaning and why it's the best solution to the out-of-scope problem, but I love how, rather than do something like just close it or mark it "not-a-problem", they use a phrase like "wontfix" that seems to imply that it is a problem, but they aren't gonna do nothin' about it. It comes across as sassy haha. |
Oh, I intend to sass, Mr. Rapp. |
The readme says I can safely ignore this repo, but neither do I wish do ignore it nor do I wish to be safe about my ignorance, should I change my mind and select ignorance. I would suggest that you re-word this to be more inclusive of the nosier among us.
You can safely ignore this issue.
The text was updated successfully, but these errors were encountered: