How to request a change to a CVE record
Learn how to identify which CVE Numbering Authority is responsible for the record, how to contact them, and what to include with your suggestion.
Learn how to identify which CVE Numbering Authority is responsible for the record, how to contact them, and what to include with your suggestion.
Supply chain attacks exploit our implicit trust of open source to hurt developers and our customers. Read our proposal for how npm will significantly reduce supply chain attacks by signing packages with Sigstore.
Do you worry that a CVE will hurt the reputation of your project? In reality, CVEs are a tracking number, and nothing more. Here’s how we think of them at GitHub.
2022-04-22 Update: Out of an abundance of caution due to the legacy nature of the app, we have moved up the deprecation timeline and the shutdown is effective immediately. The…
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…
The GitHub Social Impact and Policy teams are issuing a Request for Proposal (RFP) for a researcher to define a list of publicly available GitHub platform usage metrics by country for international development, public policy and economics disciplines.
API requests made by a GitHub App on behalf of a user that has authorized the app are known as user-to-server requests. The resources that can be accessed by these…
We’ve acquired Pull Panda to help teams create more efficient and effective code review workflows on GitHub.
The icon used when requesting changes in a pull request review has now been updated. Learn more about pull request reviews
Review requests are a great way to ask for review on software, and with the addition of team requests you can get the feedback you need faster. To make it…
Review requests are a great way to get the people you need to look at your work. Now with team requests, you can find the right group of people and…
You can now request a review explicitly from collaborators, making it easier to specify who you’d like to review your pull request. You can also see a list of people…
GitHub Flavored Markdown is getting a little Task List flavoring. Today, we’re shipping an enhancement to our Markdown pipeline to support task lists. Task lists are lists with items marked…
Dependabot keeps your dependencies current, but its defaults can flood your repository with pull requests. Here’s how grouping updates, slowing the cadence, and keeping security fixes fast cut the noise on a Microsoft open source project.
A new default three-day cooldown delays version update pull requests so maintainers and security researchers can address findings in a release before it gets into your code.
New to GitHub? This beginner’s guide explains version control, repositories, and pull requests—plus everything else you need to start working confidently on GitHub.
How migrating Copilot code review to shared Unix-style code exploration tools reduced review cost by reshaping agent workflows around pull request evidence.
Explore how the Aspire team turns merged product changes into SME-reviewed docs pull requests, closing the gap between release and documentation.
A new repository-level dataset, published on GitHub under CC0-1.0, helps researchers and developers discover multilingual developer content across READMEs, issues, and pull requests.
Agentic workflows that run on every pull request can quietly accumulate large API bills. Here’s how we instrumented our own production workflows, found the inefficiencies, and built agents to fix them.
Discover how to use GitHub Copilot directly in the terminal. From cloning a repository to opening a pull request, here’s how to streamline your workflow with Copilot CLI.
Build what’s next on GitHub, the place for anyone from anywhere to build anything.
Join us October 28-29 in San Francisco or online for GitHub Universe, our flagship developer event uniting people, agents, and the world’s code.