Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Investigate getting rid of JS Debugger category/redirecting it to debugger-html repo #31

Open
nt1m opened this issue Jan 4, 2017 · 2 comments
Open

Investigate getting rid of JS Debugger category/redirecting it to debugger-html repo #31

nt1m opened this issue Jan 4, 2017 · 2 comments

Comments

@nt1m
Copy link

nt1m commented Jan 4, 2017

Thoughts everyone?

The old debugger is no longer maintained, so recommending bugs on the deprecated tool isn't a good idea.
@captainbrosset
Copy link

Great point. If we could instead use the GH API to find "up for grabs" issues from that repo, that would be great.

@captainbrosset
Copy link

They use a bunch of labels, like difficulty: easy or up for grabs that would map quite nicely to the flags we already have in the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@captainbrosset @nt1m