-
Notifications
You must be signed in to change notification settings - Fork 13
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
Update bottom part of README #19
Comments
not sure if y'all want to take on docs for these kinds of repos, @klavavej , so feel free to remove from your project if not. |
@fool - we would consider issues for these kinds of repos if they were high priority. Since this is low priority I'm going to remove it from our board. |
Yup, hard to consider this one high priority. Guess I'll do it myself,
someday, well that means it will never happen so I'll leave the issue there
for whomever touches the repo. Thanks for being frank @klavavej
…On Tue, Feb 19, 2019 at 7:58 AM Kristen Lavavej ***@***.***> wrote:
@fool <https://github.com/fool> - we would consider issues for these
kinds of repos if they were high priority. Since this is low priority I'm
going to remove it from our board.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAN-oH5QW9WnE4ta6jH3FkbEZ9B__hPAks5vPB84gaJpZM4a-tnx>
.
|
This issue has been automatically marked as stale because it has not had activity in 1 year. It will be closed in 7 days if no further activity occurs. Thanks! |
While this is definitely long in the tooth, it is still needed - those docs are flat out wrong, so I've opted this out of the stalebot workflow. |
oh, this is kinda a dupe of #29 |
still mentions wrong things about the old PhantomJS implementation
The text was updated successfully, but these errors were encountered: