Being friendly: Friendly forks 101
This is the first post in a two-part series describing friendly forks and alternative strategies for managing them. Stay tuned for part two coming in May!
GitHub Blog Search
This is the first post in a two-part series describing friendly forks and alternative strategies for managing them. Stay tuned for part two coming in May!
We’re kicking off InFocus, a global virtual event focused on accelerating, securing, and improving the way software development teams work.
Organization profiles can now display custom content visible only to members of the organization. A new Member view can be tailored to show an alternative README and pinned private repositories.
We’re releasing exciting improvements that will streamline your Codespaces experience when working with multi-repository projects and monorepos.
On April 12, GitHub Security began an investigation that uncovered evidence that an attacker abused stolen OAuth user tokens issued to two third-party OAuth integrators, Heroku and Travis-CI, to download data from dozens of organizations, including npm. Read on to learn more about the impact to GitHub, npm, and our users.
Today, we’re excited to bring you a few new features that will help you communicate, collaborate, and connect seamlessly with teams and communities about the software you’re building with the help of GitHub Discussions.
Secret scanning: Dry runs for organization-level custom patterns
Ensuring secure access to your source code is more important than ever. Git Credential Manager helps make that easy.
Secret scanning custom pattern events now in the audit log
From automating builds and releases to taking care of large-scale regression testing, here are a few ways we use GitHub Actions to build GitHub.
Secret scanning prevents secret leaks with protection on push
Organizations with GitHub Advanced Security can now proactively protect against secret leaks with secret scanning’s new push protection feature.
Securing your projects is no easy task, but end-to-end supply chain security is more top of mind than ever. We've seen bad actors expand their focus to taking over user…
You can now enforce consistent usage of self-hosted runner groups across your organization and enterprise.
If you're a GHES customer with heavy read traffic on your monorepo, check out the repository cache, especially if you have CI workloads distributed around the world.
GitHub Actions: Restrict self-hosted runner groups to specific workflows