-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Code not pushed to github on solving #578
Comments
facing same problem |
I am also facing the same problem |
you need to revert to leetcode old theme |
@devhindo There's no option for the old theme on the study plans, for example, I can't find the old theme option for this one- https://leetcode.com/studyplan/top-interview-150/ |
facing same Issue |
same issue |
@Tanmay-901 Click a question in the study set, and when the editor opens, you should be able to click your profile picture and switch back to the old version. |
facing the same issue. https://leetcode.com/discuss/general-discussion/181563/Switch-back-to-old-UI |
@Tanmay-901 It unfortunately looks like the maintainer went inactive. There are several PRs for fixing the new UI issues, including the oldest one #464 which even got the maintainer's discussion participation in January. However, he went inactive without merging the PR, so our best bet is either using the old theme or using one of the fork that fixed this issue. I personally work on problems using the new UI (new UI's Vim mode is drastically better than the old one) and once i pass all the test cases, I revert back to old version and make a submission. It's tedious, but it's works best for me. |
Please review previous closed issues before filling out a new one! Duplicate issues will be closed without comment.
Describe the bug
I've installed the extension recently and created a repo using it, but the code is not getting pushed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should've showed the problem solved in extension and github repo
Screenshots
The text was updated successfully, but these errors were encountered: