Trending repository
-
Updated
Jul 4, 2021 - Jupyter Notebook
Your favorite open source projects and the developers who make them happen. Listen in!
November 01, 2021 - December 01, 2021 • Online
nvim --version:NVIM v0.5.0-dev+1339-g5d9c56012
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/T
ools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2
/Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC
Tired of manually scraping your code looking for the smallest issues? Take codebeat for a spin!
codebeat is an automated static code analysis tool supporting multiple languages used by both web and mobile developers worldwide. Now also providing style analysis for projects written in Swift
We've integrated SwiftLint, the best linter for Swift in our code review app and fixed you with a help page. about the feature. Enjoy!
Here is a list of links that return 404
https://apility.io/apidocs/
http://developer.linkedin.com/docs/rest-api
https://sentim-api.herokuapp.com/ works
https://quarantine.country/coronavirus/api/ works
https://blog.mugenmonkey.com/2017/09/10/ds3-api.html
https://developer.walmartlabs.com/docs
https://taylor.rest
Please feel free to add more broken links when you find t
We need either an automated process or manual guideline for releasing new versions of Scorecard. Basically, when users run the below command, we need to be sure to a high degree of confidence that this is well tested code that users are downloading and running:
GO111MODULE=on go get github.com/ossf/scorecard
GITHUB_AUTH_TOKEN="xyz" scorecard --repo=<repo-name> --show-details
Language informations
A Dependently typed programming language with complex grammar parsing, Treesitter-agda is dead though
The Storybook API has changed quite a lot since Solid's Storybook docs were written in 2019. It would be really helpful (and I think go a loooong way toward helping drive adoption, long-term) if Solid could:
Code Climate combines line-by-line test coverage reports, technical debt assessments, and style checks in every pull request so that your team only merges clear, maintainable, and well-tested code.
Like this one: https://github.com/Mofiqul/vscode.nvim
porting spacegray should be first