As the world becomes more interconnected and complicated, so too does the expanse of open source ecosystems. While the majority of open source software (OSS) lies with corporate technology companies, in the last year, the
As GitHub doubled it’s developer head count, tooling that worked for us no longer functioned in the same capacity. We aimed to improve the deployment process for all developers at GitHub and mitigate risk associated with deploying one of the largest developer platforms in the world.
It’s no secret that making your first contribution to open source can be intimidating. A Major League Hacking survey found that a majority of students know that contributing to open source is important for their
If you haven’t seen it, the GitHub Changelog helps you keep up-to-date with all the latest features and updates to GitHub. We shipped a tonne of changes last year, and it’s impossible to blog about
On Friday, January 8th, GitHub separated with an employee. Later that day and over the weekend, employees raised concerns about the circumstances of the separation. We took these concerns seriously. On Monday, January 11th, we
Today, we’re making GitHub Enterprise Server 3.0 available as a release candidate. Announced in the GitHub Universe Keynote, it’s the biggest ever change to Enterprise Server, bringing customers: Actions – developer-first workflow automation and CI/CD
We’ve made huge advances in our security features at GitHub in 2020, with launches for code scanning, secret scanning, Dependabot version updates, dependency review, and more.
In December, we experienced no incidents resulting in service downtime. This month’s GitHub Availability Report will provide a summary and follow-up details on how we addressed an incident mentioned in November’s report.
GitHub’s engineering group moved from a monolithic, hero-based on-call rotation to a more balanced on-call culture in order to increase our on-call expertise and improve the experience for our customers.
阅读中文版本 推动开发者自由： GitHub 在伊朗现已完全可用 无论开发者身在何处，都应该有权自由使用GitHub。与此同时，GitHub 也尊重并且遵守美国法律，也就意味着政府制裁限制了我们向某些国家的开发人员所提供的 GitHub 服务。 今天，我们郑重宣布一项重大进展：我们已经取得了美国政府颁发的许可证，可以向伊朗的开发者提供 GitHub 服务，其中包括面向个人和组织的所有服务，包括私人和公共的免费与付费服务。 所以具体情况是什么？ 美国长期以来对包括伊朗在内的多个国家实施了广泛制裁。 这些制裁措施禁止任何美国公司与受制裁国家中的任何人进行商业往来。 （这些制裁措施也可以适用于其活动直接或间接涉及美国的非美国公司，包括使用美国的银行或Visa之类的付款机制进行的支付。） 因此，在 2019 年，GitHub 对伊朗和其他几个国家/地区的开发者实施了访问权限限制，以遵守美国制裁法。 但与此同时，为了实现让所有人都能使用 GitHub 的目标，我们还立即采取了另外两项措施： 首先，在服从制裁政策的同时，我们按照美国制裁法律的规定，竭尽所能地 [让尽可能多的开发者们使用尽可能多的 GitHub 服务] (https://github.blog/2019-09-12-global-software- collaboration-in-the-face-of-sanctions/)，甚至在被制裁国家/地区提供了公共代码库。 另外，我们向美国财政部下属的海外资产控制办公室 (OFAC) 反映了情况，并就争取在被制裁国家/地区提供广泛开放的 GitHub 服务与其展开了漫长且紧张的谈判。 在两年的时间内，我们展示了开发者如何使用 GitHub 推动人类进步、国际交流，以及美国长期以来秉持的促进自由言论和信息自由流通的外交政策。我们非常感谢
