-
Updated
Dec 30, 2020 - Python
Here's what's popular on GitHub today...
-
Updated
Mar 2, 2021
View a 3D model of your GitHub contribution graph. Share it, print it, and more!
-
Updated
Mar 3, 2021 - VBA
-
Updated
Mar 1, 2021 - Java
GitHub CTF - A Call to Hacktion!
March 17, 2021 - March 21, 2021 • Online
-
Updated
Dec 26, 2020 - Shell
GitHub Learning Lab
Level up your skills with GitHub Learning Lab. Our friendly bot will take you through a series of fun, practical projects to learn the skills you need in no time—and share helpful feedback along the way.
-
Updated
Mar 3, 2021 - Kotlin
Add CMake aliases
GTest exports the following targets:
GTest::gtestGTest::gtest_mainGTest::gmockGTest::gmock_main
This targets should also be available when adding gtest with add_subdirectory (or FetchContent), because this should behave the same way as adding GTest with find_package. So somewhere, we should add the aliases to these targets, i.e.
add_library(GTest::gtest ALIAS
-
Updated
Feb 5, 2021 - Objective-C
Summary
Consider the following workflow:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: changing-conditional-
spec:
entrypoint: plan
templates:
- name: plan
steps:
- - name: set-global-parameter
template: global-parameter-setting
arguments:
parameters:
- name: setting
value: true
-
Updated
Mar 3, 2021 - Python
-
Updated
Mar 1, 2021 - Swift
-
Updated
Feb 28, 2021 - JavaScript
Improvement
Update the code base by removing unused imports in ignite. This can be easily found by removing F401 in setup.cfg.
Previous PRs are done for examples in #1703 and tests in #1707
Only ignite package left now. Modules TBD:
-
ignite.base -
ignite.contrib.engines -
ignite.contrib.handlers -
ignite.contrib.metrics -
ignite.distributed - [
-
Updated
Feb 22, 2021 - Shell
-
Updated
Mar 3, 2021 - Objective-C
-
Updated
Feb 27, 2021 - C++
-
Updated
Mar 2, 2021 - Python
-
Updated
Mar 3, 2021 - Go
-
Updated
Mar 3, 2021 - Go
-
Updated
Feb 27, 2021 - Ruby
Stale
Automatically close stale Issues and Pull Requests that tend to accumulate during a project.
How it works
After a period of inactivity, a label will be applied to mark an issue as stale, and optionally post a comment to notify contributors that the Issue or Pull Request will be closed.
If the Issue or Pull Request is updated, or anyone comments, then the stale label is removed.
If no more activity occurs, the Issue or Pull Request will be automatically closed with an optional comment.
The asset ordering in the
/tradesendpoint is not deterministic. See, for example how responses are different for the same request (/trades?cursor=133053547049738241-0&limit=10&order=asc) in https://horizon.stellar.org/ vs https://horizon-stg-pubnet.stellar.org/.The ordering sho