-
Updated
Apr 19, 2021 - Python
Here's what's popular on GitHub today...
-
Updated
Apr 18, 2021 - C++
Control and monitor every aspect of your 3D printer and your printing jobs right from within your browser.
Atom
-
Updated
Apr 19, 2021
-
Updated
Apr 14, 2021 - Python
-
Updated
Apr 15, 2021 - GLSL
CodeFactor
Ensure that your code meets quality standards
CodeFactor instantly performs Code Review with every GitHub Commit or PR. Zero setup time. Get actionable feedback within seconds. Customize rules, get refactoring tips and ignore irrelevant issues.
Languages
Bash, C, C#, C++, CoffeeScript, CSS, Dockerfile, Go, Groovy, Java, JS, Kotlin, Less, PHP, Python, Ruby, Scala, SCSS, Sugar SS, Swift, TypeScript and YAML.
Autofix
Autofix certain reported issues on-demand or automatically.
-
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
Layer CI
Ship code faster with LayerCI
Developers move much faster using LayerCI to get per-branch review & E2E testing environments.
- It's easy to write efficient tests with our familiar Docker-like syntax. Never see a huge YAML file again.
- Get a staging server per-commit by adding
EXPOSE WEBSITEto the bottom of your pipeline configuration - Skip repetitive setup with our industry-leading Layer cache, it's like "docker build" but supercharged specifically for CI.
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