We prepared a dataset from the GH Archive that contains all the events in all GitHub repositories since 2011 in structured format. The dataset was uploaded into ClickHouse, where it contains 3.1 billion records. We redistribute it for research purposes and it can be downloaded at this direct link. This dataset can help answer almost any question about GitHub that you can imagine.
- Counting stars
- Top repositories by stars
- Distribution of repositories by star count
- The total number of repositories on GitHub
- How has the list of top repositories changed over the years?
- How has the total number of stars changed over time?
- Who are all those people giving stars?
- Repository affinity list
- Finding friends through counting stars
- Affinity by issues and PRs
- Repositories with the most stars over one day
- Repositories with the highest growth YoY
- Repositories with the worst stagnation
- Repositories with the most steady growth over time
- What is the best day of the week to catch a star?
- The total number of users on GitHub
- Stars from heavy GitHub users
- Repositories with the maximum amount of pull requests
- Repositories with the maximum amount of issues
- Repositories with the most people who have push access
- Repositories with the maximum number of accepted invitations
- Most forked repositories
- Proportions between stars and forks
- Issues with the most comments
- Top commented issues for each of the top repositories
- Commits with the most comments
- The most tough code reviews
- Authors with the most pushes
- Organizations by the number of stars
- Organizations by the number of repositories
- Organizations by the size of community
- Repositories by amount of modified code
- Repositories by the number of pushes
- Authors with the most code reviews
- Top labels
- The longest repository names
- The shortest repository names
- Repositories with ClickHouse-related comments
- Most popular comments on GitHub
- GitHub roulette
-
所以现在我们已经介绍了 GitHub 的大部分功能与工作流程，但是任意一个小组或项目都会去自定义，因为他们想要创造或扩展想要整合的服务。 对我们来说很幸运的是，GitHub 在许多方面都真的很方便 Hack。 在本节中我们将会介绍如何使用 GitHub 钩子系统与 API 接口，使 GitHub 按照我们的设想来工作。 钩子 GitHub 仓库管理中的钩子与服务区块是 GitHub 与外部系统交互
-
你可以在 Github 上为项目创建远程仓库。创建公开的远程仓库是免费的，私有仓库要收费。 任务 在 Github 网站申请一个帐号。 https://github.com 配置帐号的 ssh-key。 https://github.com/settings/keys ssh-key 在 Github 个人帐户里配置使用了 ssh-key，以后你往你的 Github 远程仓库推送的时候就不需要输入
-
代码仓库 我们在GitHub上进行Tengine项目的开发：https://github.com/alibaba/tengine。 可以用git检出最新的Tengine代码： 参与开发 我们非常欢迎也很鼓励您在Tengine的项目的GitHub上报告issue或者pull request。 如果您还不熟悉GitHub的Fork and Pull开发模式，您可以阅读GitHub的文档（https:/
-
类属性 $allowSignup 是否在登录页显示注册，默认false
-
推荐大家使用 https://gitee.com 速度更快，项目直接部署、Android 自动构建！ 私有库永久免费，提供手机客户端，国内首个同时支持 Git 和 SVN 的代码托管平台） 如何一键导入 Github 仓库：https://blog.gitee.com/2018/06/05/github_to_gitee/ GitHub 可以托管各种 git 库，并提供一个 Web 界面，但与
-
在本章中，我们将向您展示如何使用GitHub API对用户进行身份验证。 步骤1 - 启用GitHub身份验证 打开Firebase仪表板，然后单击侧面菜单中的Auth ，然后单击标签栏中的SIGN-IN-METHOD 。 您需要启用GitHub身份验证并复制Callback URL 。 您将在步骤2中使用此选项。您可以打开此选项卡，因为完成第2步后需要添加Client ID和Client Sec