Search results for: repository

It’s now possible to ignore revisions in the blame view using a .git-blame-ignore-revs file in the root of your repository. For more information, see “Ignore commits in the blame view”.

You can now enforce consistent usage of self-hosted runner groups across your organization and enterprise.

You can now create a branch to work on an issue directly from the issue page so that it’s easier to get started right away.

GitHub secret scanning protects users by searching repositories for known types of secrets. By identifying and flagging these secrets we help protect users from data leaks and fraud associated with…

Our community has shipped lots of open source project updates in the last month. Here’s a few of our staff picks.

Dependency caching is one of the most effective ways to make jobs faster on GitHub Actions. You can now monitor the storage usage of your existing caches and get greater…

It is now possible to re-run only failed jobs or a single job in GitHub Actions workflows.

Today, we are sharing new updates to the projects (Beta) experience, including updated repository filters and custom charts for project insights. We are also sharing a preview of issues closed…

Repository owners can now configure tag protection rules to protect tags in all public repositories and in private repositories on the Pro, Teams or Enterprise plans on GitHub. Once protected…

GitHub Advanced Security customers can now scan their public repositories using Advanced Security secret scanning. Like scanning on private repositories, scanning on public repositories can be enabled at the repository,…

Support for Actions in internal repositories is now generally available for GitHub organizations owned by an enterprise account. You can innersource automation by sharing Actions in internal repositories, without publishing…

GitHub code scanning helps open source maintainers and organizations find potential vulnerabilities in their code, before these can make their way into deployments. CodeQL, our very own analysis engine, powers…

Today, we’re announcing that the ability to prebuild codespaces is entering public beta. Prebuilding a codespace enables fast environment creation times, regardless of the size or complexity of your repositories.…

The ability to prebuild codespaces is entering public beta. Enable fast environment creation times, regardless of the size and complexity of your repositories.

GitHub code scanning supports a wide variety of code analysis engines through GitHub Actions workflows — including our own CodeQL engine. Users can now discover and configure Actions workflow templates…

GitHub Actions workflows in the Security category will now appear among the workflow recommendations based on a repository’s content.

Are you using our GitHub app in Microsoft Teams or Slack? Do you find it difficult to track all the notifications you get in your channels? If yes, here comes…

Anyone can now provide additional information to further the community’s understanding and awareness of security advisories.

A CODEOWNERS file defines the users or teams responsible for different parts of your repository, and helps ensure the right people are included in pull request reviews. We’ve shipped some…

Today we launched new code scanning analysis features powered by machine learning. The experimental analysis finds more of the most common types of vulnerabilities.

A behind-the-scenes peek into the machine learning framework powering new code scanning security alerts.