The Wayback Machine - https://web.archive.org/web/20200919102434/https://github.com/explore
Skip to content

Join GitHub (or sign in) to find projects, people, and topics catered to your interests.

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

GitHub CLI 1.0 is here

Take GitHub to the command line. GitHub CLI 1.0 is now available for Windows, macOS, and Linux! Download it for free now.

Ethereum logo
Popular topic
Ethereum is a distributed public blockchain network.
App recommended by GitHub

Percy

Percy gives your team confidence in every visual UI change before it's shipped.

Percy adds visual reviews to your GitHub pull requests, helping your team spot UI bugs quickly and review visual changes easily.

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

A modern desktop interface for Linux. Improve your user experience and get rid of the anarchy of traditional desktop workflows. Designed to simplify navigation and reduce the need to manipulate windows in order to improve productivity. It's meant to be 100% predictable and bring the benefits of tools coveted by professionals to everyone.

  • Updated Sep 17, 2020
  • JavaScript
Trending repository
ezyang
ezyang commented Aug 18, 2020
WARNING: /data/users/ezyang/pytorch-tmp/BUILD.bazel:580:1: in hdrs attribute of cc_library rule //:aten_headers: Artifact 
'bazel-out/k8-fastbuild/bin/aten/src/ATen/Config.h' is duplicated (through '//:aten/src/ATen/Config.h' and '//:aten_src_AT
en_config'). Since this rule was created by the macro 'cc_library', the error might have been caused by the macro implemen
tation                 
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.

You can’t perform that action at this time.