Skip to content

Here's what's popular on GitHub today...

GitHub Skyline
Staff pick

View a 3D model of your GitHub contribution graph. Share it, print it, and more!

Kubernetes logo
Popular topic
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications.
GitHub CTF - A Call to Hacktion!
Upcoming event recommended by GitHub
Mar
17

GitHub CTF - A Call to Hacktion!

March 17, 2021 - March 21, 2021 • Online

The GitHub Security Lab CTF is a contest where participants are challenged to leverage software vulnerabilities to solve a real world security puzzle.
Trending repository
App recommended by GitHub

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.

Trending repository
lukasm91
lukasm91 commented Aug 24, 2019

GTest exports the following targets:

  • GTest::gtest
  • GTest::gtest_main
  • GTest::gmock
  • GTest::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 
Trending repository
Trending repository

Demisto is now Cortex XSOAR. Automate and orchestrate your Security Operations with Cortex XSOAR's ever-growing Content Repository. Pull Requests are always welcome and highly appreciated!

  • Updated Mar 3, 2021
  • Python
Trending repository
ydcjeff
ydcjeff commented Mar 2, 2021

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
  • [
App recommended by GitHub

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.