-
Updated
Apr 16, 2021 - C++
Here's what's popular on GitHub today...
-
Updated
Apr 17, 2021 - TypeScript
Control and monitor every aspect of your 3D printer and your printing jobs right from within your browser.
-
Updated
Apr 16, 2021 - Python
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
-
Updated
Apr 17, 2021 - C++
Code Inspector
Code Inspector is a code analysis platform that does automated code reviews, technical debt management and analysis of code quality trends over time. The platform aggregates multiple quality metrics (violations, duplicates, readability, complexity). The platform reports the $ figure of the technical debt and show trends of your code base. Code Inspector reports the most critical issues by distinguishing them according to their category, severity and location.
-
Updated
Apr 17, 2021 - Python
-
Updated
Jan 6, 2021
-
Updated
Apr 17, 2021 - C#
-
Updated
Apr 16, 2021 - Python
Describe the bug
When I try to fork a repo and add a new remote, it doesn't add a new remote to my current repository.
gh version 1.4.0 (2020-12-17)
Expected vs actual behavior
I expect to see a fork remote added to my repository, but nothing is added.
Logs
❯ gh repo fork --clone=false --remote=true $(git remote get-url up)
- Forking someorg/somerepo...-
Updated
Apr 16, 2021 - HTML
-
Updated
Apr 16, 2021
-
Updated
Apr 16, 2021 - Python
-
Updated
Apr 16, 2021 - C#
-
Updated
Apr 15, 2021 - GLSL
-
Updated
Apr 16, 2021 - HTML
Right now the MustBeExecutedContextExplorer Explorer is created without analysis, e.g., without a dominator tree. As a consequence it is not able to determine non-trivial control flow merge points which reduces the "must-be-executed-context" substantially.
The task is to provide the appropriate analysis getters to the Explorer during creation and update the tests accordingly. If tests for t
-
Updated
Apr 15, 2021
-
Updated
Apr 15, 2021
GitKraken Boards
GitKraken Boards syncs in real-time with GitHub Issues and GitHub Milestones so changes made in either system are immediately reflected in the other. Link cards to GitHub pull requests, check PR statuses, auto-update cards based on PR statuses and view build statuses without leaving GitKraken Boards.
Plus, use GitHub Actions to automate your workflow; trigger automated actions in GitKraken Boards by linking cards to pull requests descriptions or commit messages in GitHub.
Build an example
Is your feature request related to a problem? Please describe.
New example use-case
Describe the solution you'd like
We've had a few people ask if they can use Supabase directly in their Webflow project. We don't know for sure, but we suspect you can if you're on Webflow's paid plan (so that you can add custom code).
You can already use supabase on a static