-
Updated
Jul 26, 2020 - JavaScript
Join GitHub (or sign in) to find projects, people, and topics catered to your interests.
Here's what's popular on GitHub today...
-
Updated
Jul 26, 2020
Ubuntu
-
Updated
Jul 25, 2020 - JavaScript
Vulnerability economics: understanding the real value of security flaws in software
July 30, 2020 • Virtual
-
Updated
Jul 25, 2020 - Python
Text editors
The text editor is a sacred application for developers. Here's a showcase of some amazingly awesome open source editors.
Review Notebook App
Having trouble using Jupyter Notebooks effectively in your team? Join 200+ organizations like Amazon, Microsoft, Tensorflow, fast.ai in using ReviewNB for notebook code reviews.
We provide complete code review workflow for notebooks,
- Visual diff to see what changed in a notebook
- Commenting on the notebook diff to discuss changes
- Conversation threads to track all open discussions
-
Updated
Jul 24, 2020
-
Updated
Jul 25, 2020 - JavaScript
-
Updated
Jul 14, 2020 - HTML
-
Updated
Apr 2, 2020
-
Updated
Jul 24, 2020 - Python
-
Updated
Jul 14, 2020 - PHP
-
Updated
Jul 25, 2020 - Kotlin
-
Updated
Jul 17, 2020 - JavaScript
-
Updated
Jul 26, 2020 - Rust
-
Updated
May 31, 2020 - Go
-
Updated
Jul 25, 2020 - Python
-
Updated
Jul 24, 2020 - TypeScript
-
Updated
Jul 26, 2020
-
Updated
Jul 26, 2020 - Python
-
Updated
Jul 24, 2020
-
Updated
Jul 24, 2020 - Python
-
Updated
Jul 25, 2020 - C++
-
Updated
Jul 25, 2020 - Swift
-
Updated
Jul 26, 2020 - TypeScript
Stale
Automatically close stale Issues and Pull Requests that tend to accumulate during a project.
How it works
After a period of inactivity, a label will be applied to mark an issue as stale, and optionally post a comment to notify contributors that the Issue or Pull Request will be closed.
If the Issue or Pull Request is updated, or anyone comments, then the stale label is removed.
If no more activity occurs, the Issue or Pull Request will be automatically closed with an optional comment.