Skip to content

GitHub Blog Search

Search Results for: repository

An illustration of two octocats repairing a robot.

Auto-watching updates

If you create a user-owned repository, you will now be automatically watching it for updates. Forks will no longer be automatically watched, even if you are granted push access. Learn…

Becca Zandstein
null

Introducing new ways to keep your code secure

It’s more important than ever that every developer becomes a security developer—that they responsibly disclose vulnerabilities and patch vulnerable code quickly. Today, we’re excited to announce several new security features designed to make it easier for developers to secure their code.

Justin Hutchings
An illustration of two octocats repairing a robot.

Community contributors

Users can hover over a repository's contributor count, and community contributors will show a hovercard of direct and transitive contributors to dependencies parsed from that repository's dependency graph. Learn more…

Stephanie Wills
An illustration of two octocats repairing a robot.

Security policy

Repositories may now specify a security policy by creating a file named SECURITY.MD. This file should be used to instruct users about how and when to report security vulnerabilities to…

Stephanie Wills
Git ransom campaign incident report—Atlassian Bitbucket, GitHub, GitLab

Git ransom campaign incident report—Atlassian Bitbucket, GitHub, GitLab

Today, Atlassian Bitbucket, GitHub, and GitLab are issuing a joint blog post in a coordinated effort to help educate and inform users of the three platforms on secure best practices relating to the recent Git ransomware incident. Though there is no evidence Atlassian Bitbucket, GitHub, or GitLab products were compromised in any way, we believe it’s important to help the software development community better understand and collectively take steps to protect against this threat.

John Swanson