-
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.
Ethereum
-
Updated
Apr 19, 2021
-
Updated
Apr 14, 2021 - Python
-
Updated
Apr 15, 2021 - GLSL
Issue-Label Bot
Issue Label Bot automatically labels issues as either a feature request, bug or question, using machine learning. You can alias these labels so that the labels are personalized for your repo (for example if you prefer enhancement vs. feature_request).
Instructions on how to alias the labels can be viewed on the app's website.
This app only works on public repositories.
-
Updated
Apr 19, 2021 - C
-
Updated
Apr 19, 2021 - C++
-
Updated
Apr 16, 2021 - HTML
-
Updated
Apr 18, 2021 - Python
-
Updated
Apr 19, 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
Mergify
Mergify is a pull requests automation service. It allows you to trigger actions when your pull requests match defined criteria.
In a few lines of YAML, you could write a rule that automatically merges a pull request if:
- it has been approved
- the test suite passes
We have plenty of examples.
Mergify executes actions for you, freeing you from the burden of managing your pull requests.
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