-
Updated
Jan 12, 2021 - Java
Here's what's popular on GitHub today...
-
Updated
Jan 11, 2021 - Java
Vim
-
Updated
Jan 11, 2021 - Swift
-
Updated
Jan 11, 2021 - JavaScript
-
Updated
Jan 12, 2021 - Go
Pixel Art Tools
Creating pixel art for fun or animated sprites for a game? The digital artist in you will love these apps and tools!
CircleCI
Now supporting GitHub Checks!
You can now see the status of your CircleCI workflows and related jobs all within the GitHub UI. Enable this feature in your CircleCI organization settings for new and existing accounts.
Build faster. Test more. Fail less.
Let CircleCI help your team focus on making a great product. Speed up your test and delivery cycle and improve productivity, without running your own infrastructure.
-
Updated
Jan 11, 2021 - C++
-
Updated
Jan 12, 2021 - C
-
Updated
Jan 12, 2021 - Ruby
-
Updated
Jan 10, 2021 - TypeScript
-
Updated
Jan 11, 2021 - Python
-
Updated
Jan 11, 2021
-
Updated
Jan 10, 2021
-
Updated
Jan 12, 2021 - Kotlin
-
Updated
Jan 11, 2021 - JavaScript
-
Updated
Jan 5, 2021 - Jupyter Notebook
-
Updated
Jan 12, 2021
-
Updated
Jan 7, 2021 - Jupyter Notebook
-
Updated
Jan 11, 2021
-
Updated
Jan 11, 2021 - Shell
-
Updated
Jan 12, 2021 - Go
Errors:
126. new Intl.NumberFormat is not supposed to get passed a single object as param. The first param must be a string and the second param can be an object.
135. Spelling error ('tis' should be 'this').
Suggestion:
86. Needs to be more explicit by calling the function in the example. Calling getName() with any falsy value would not set hasName to true with your correct answer.
-
Updated
Jan 11, 2021 - Python
-
Updated
Jan 5, 2021 - Jupyter Notebook
LGTM
Continuous security analysis
LGTM is a code analysis platform for identifying vulnerabilities and preventing them from reaching production.
LGTM automatically runs 1600+ standard analyses contributed by researchers from the Semmle Security Research Team and our customer community, including Microsoft, Google, Uber and Mozilla.
Quickly refine and run custom QL queries to find variants of known issues and prevent them from being re-introduced into your codebase.


Displaying the current tool number {after T0/T1/T2/...) on the screen would be helpful with MMU2 or other toolchanger.
The number can be displayed inside the nozzle picture.