-
Updated
Apr 19, 2021 - Python
Here's what's popular on GitHub today...
-
Updated
Apr 18, 2021 - C++
View a 3D model of your GitHub contribution graph. Share it, print it, and more!
Firebase
-
Updated
Apr 19, 2021
-
Updated
Apr 14, 2021 - Python
-
Updated
Apr 15, 2021 - GLSL
Text editors
The text editor is a sacred tool for developers. Here's a showcase of some amazingly awesome open source editors.
Sider
Sider checks code using custom rules based on project specific knowledge and cumulative team experiences. On each pull request, Sider automatically alerts developers on previously documented issues and key information relevant to the changed code.
-
Updated
Apr 19, 2021 - C
-
Updated
Apr 17, 2021 - C++
-
Updated
Apr 16, 2021 - HTML
-
Updated
Apr 18, 2021 - Python
-
Updated
Apr 16, 2021 - Python
-
Updated
Apr 17, 2021 - Java
-
Updated
Apr 8, 2021 - Python
-
Updated
Apr 19, 2021 - C++
fuzzing: Use `wasm-encoder` rather than generating WAT text and then assembling it in dummy imports
In bytecodealliance/wasmtime#2497 (comment) we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to Module::new which internally checks for WAT strings and assembles them into Wasm bytes if necessary.
We can make this more efficient, improving the number of test cases we fuzz in a
-
Updated
Apr 15, 2021
-
Updated
Apr 8, 2021 - Python
document in CONTRIBUTING.md that REST content is autogenerated and should not be modified by mortals
-
Updated
Apr 19, 2021
-
Updated
Jan 6, 2021
-
Updated
Apr 12, 2021 - Java
-
Updated
Jan 16, 2021
Travis CI
Travis CI enables your team to test and ship your apps with confidence. It’s built for everyone and for projects and teams of all sizes, supporting over 20 different languages out of the box, including Javascript and Node.js, Ruby, PHP, Python, Mac/iOS, as well as Docker, while giving you full control over the build environment to customize it to your own needs.
Travis CI is trusted by hundreds of thousands of open source projects, teams, and developers.
The "from Hits" portion isn't supported. I don't believe there are any sources of bleeding that come from non-hits, so that could potentially be added in the same place as
Damage over Time Multiplier for Bleeding