What’s inside:
- A checklist for safeguarding your entire software supply chain—from reviewing and implementing platform security fundamentals to protecting your codebase and build system
- Tips and resources for integrating AI and automation at specific steps in the software supply chain 

Powering DevSecOps with AI and automation can help prevent developers from writing vulnerable code in the first place, generate secure code suggestions that developers can test and refine, and provide context around potential vulnerabilities—all within the developer’s typical workflow. As a result, organizations can save costs by catching and fixing vulnerabilities in the development process rather than in production or after release. 

Form_Gated_PDF "Get the checklist"

Tell us a bit about you.

Get the checklist

Simply bolting security tools onto a developer’s workflow can create friction, and make it difficult to detect and remediate vulnerabilities. Here’s where AI can help. In this checklist, we’ll show you where and how to integrate AI and automation into your software supply chain.

Security - Dark 1

Resource Page for /security/ai-powered-devsecops-checklist

CDL: 433173

A checklist for AI-powered DevSecOps

## The GitHub Copilot Impact Glossary
This glossary lists a number of measures that an organization can use to help evaluate the impact of Copilot for their organization. Learn:
- Definitions and caveats related to measures
- When (which stage) to use a measure
- How to access a measure (source data location)

For more information on GitHub’s approach to measuring Copilot Impact, check out our [GitHub Copilot Learning Pathway](https://resources.github.com/learn/pathways/copilot/essentials/measuring-the-impact-of-github-copilot/).

Remember 😀: The relevance and usefulness of system-level speed and quality measures vary across organizations. Any Copilot impact beyond coding is indirect, and the downstream possibilities are endless. Thus, we must be careful when searching for causality in speed and quality measures. 

The metrics provided below are representative of processes that often improve with Copilot, but the degree of impact will vary. Based on the strengths and weaknesses of your organization, the impact may be more or less. It's less important to achieve a benchmark than to observe neutral-to-positive improvement. Engineering leaders should only be concerned if a metric regresses. In that case, pause to determine the root cause before proceeding.

### Tips: 
- GitHub recommends looking for improvements in each measure over time rather than setting fixed targets.
- We suggest aligning measurement frequency with your development cadence (e.g. sprint cycles).
- You may choose to collate your data points into existing BI or reporting tools for ease of analysis and review over time for trends. Alternatively, use a spreadsheet to track measures over time.
- As you add developers to Copilot you may see a decrease in some measures as those developers build capability and confidence in using Copilot as part of their daily flow. Consider analyzing measurements according to onboarding groups (set of developers provided with a Copilot seat).
- You may choose to monitor some DevOps metrics over the evaluation and adoption stages for early indicators of likely system- impact areas. But particularly in the evaluation and adoptions stages, we recommend focusing on happiness and engagement measures. Once developers are using Copilot effectively, system level measures are more likely to improve. 

### Category legend:
Developer Happiness - 😃 <br />
Developer Engagement - 👩‍💻<br />
Speed - 🏎️ <br />
Quality - ✨

<table>
    <tr>
        <th>Measure</th>
        <th>Definition</th>
        <th>Stage</th>
        <th>Source data location</th>
    </tr>
    <tr>
        <td>Satisfaction using Copilot - 😃</td>
        <td>Number of Copilot users who value Copilot in their workflow.</td>
        <td>All</td>
        <td>Copilot Impact Survey:<br />• How would you feel if you could no longer use Copilot?</td>
    </tr>
    <tr>
        <td>Benefits of using Copilot - 👩‍💻</td>
        <td>Range of areas in which users leverage Copilot and the range/extent of benefits experienced.</td>
        <td>All</td>
        <td>Copilot Impact Survey:<br />• When using Copilot, I…<br />• When using Copilot, my team…<br />• In using Copilot in the last week…<br />• I use GitHub Copilot to…</td>
    </tr>
    <tr>
        <td>Challenges using Copilot - 👩‍💻</td>
        <td>Number of users impacted by potential adoption barriers.</td>
        <td>All</td>
        <td>Copilot Impact Survey:<br />• What challenges have you encountered during your Copilot trial?</td>
    </tr>
    <tr>
        <td>Enablement provided - 👩‍💻</td>
        <td>Number of users with a seat who have received enablement resources/training sessions.</td>
        <td>All</td>
        <td>Copilot Impact Survey:<br />• Which of the following GitHub Copilot enablement materials have you received?</td>
    </tr>
    <tr>
        <td>Average Daily Active Users per Month - Completions - 👩‍💻</td>
        <td>Users who have received 1+ suggestions on a given day.</td>
        <td>All</td>
        <td>Copilot Metrics API:<br />• Take average of Active Users - Completions from API, over 28 days</td>
    </tr>
    <tr>
        <td>Average Daily Active Users - Chat - 👩‍💻</td>
        <td>Users who have 1+ chats on a given day.</td>
        <td>All</td>
        <td>Copilot Metrics API:<br />• Take average of Active Users - Chats from API, over 28 days</td>
    </tr>
    <tr>
        <td>Average Daily Active Users - Total - 👩‍💻</td>
        <td>Unique users who have received and accepted 1+ suggestions OR participated in 1+ chats on a given day.</td>
        <td>All</td>
        <td>Copilot Metrics API:<br />• Take average of Active Users - Total from API, over 28 days</td>
    </tr>
    <tr>
        <td>Suggestions Delivered - Completions - 👩‍💻</td>
        <td>Number of suggestions per day displayed in the code editor for Copilot completions in IDE.</td>
        <td>All</td>
        <td>Copilot Metrics API:<br />• Number of Suggestions</td>
    </tr>
    <tr>
        <td>Number of Acceptances - Completions - 👩‍💻</td>
        <td>Number of suggestions accepted (total of both partial and full) per day.</td>
        <td>All</td>
        <td>Copilot Metrics API:<br />• Number of Chat/code acceptances</td>
    </tr>
    <tr>
        <td>Lines of Code Accepted - Completions - 👩‍💻</td>
        <td>Lines of code accepted (total of both partial and full) accepted per day</td>
        <td>All</td>
        <td>Copilot Metrics API:<br />• Lines of Code Accepted - Completions</td>
    </tr>
    <tr>
        <td>Total Acceptance rate - Completions - 👩‍💻</td>
        <td>Suggestions Accepted (Combined: Full and Partial) / Total Number of Suggestions</td>
        <td>All</td>
        <td>Manual calculation (based on Copilot Metrics API):<br />• Number of Suggestions &<br />• Number of Acceptances</td>
    </tr>
    <tr>
        <td>New seats added in billing cycle - 👩‍💻</td>
        <td>Additional seats purchased for organizational members during this billing cycle</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>Billing and plans (Copilot) (organizational settings)<br />• New seats added during this billing cycle</td>
    </tr>
    <tr>
        <td>Dormant users - 👩‍💻</td>
        <td>Number of users who last used Copilot more than ‘n’ days ago</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>Copilot Access Management (organizational settings):<br />• Sort by last used</td>
    </tr>
    <tr>
        <td>Total completed pull requests - 🏎️</td>
        <td>Total number of pull requests completed in a given week</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>GitHub PRs list (in a repo) can be filtered on closed PRs for a time period</td>
    </tr>
    <tr>
        <td>Pull requests per developer - 🏎️</td>
        <td>Number of pull requests / code contributors</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>Manual calculation:<br />• GitHub PRs list (in a repo) can be filtered on closed PRs for a time period &<br />• Your organization's data on developers contributing to repo</td>
    </tr>
    <tr>
        <td>Time to merge - 🏎️</td>
        <td>Average time from PR opened to merge</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>GitHub: calculation requires consideration of your organization's GitHub set-up</td>
    </tr>
    <tr>
        <td>PR lead time - 🏎️</td>
        <td>Average time from PR opened to deploy</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>GitHub Actions: calculation requires consideration of your organization's GitHub set-up</td>
    </tr>
    <tr>
        <td>Code Review Time - 🏎️</td>
        <td>Average code review time per pull request (time between PR opened to PR closed)</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>GitHub: calculation requires consideration of your organization's GitHub set-up</td>
    </tr>
  <tr>
        <td>Pull request merge rate - ✨</td>
        <td>Total number of successful builds completed in a given week.</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>GitHub: GitHub PRs list (in a repo): The number of PRs merged / The number of PRs submitted</td>
    </tr>
    <tr>
        <td>Total successful builds - ✨</td>
        <td>The percentage of pull requests successfully merged</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>GitHub Actions: calculation requires consideration of your organization's GitHub set-up</td>
    </tr>
    <tr>
        <td>Change failure rate - ✨</td>
        <td>Percentage of code deployments that caused a failure in production</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>Calculation requires consideration of your organization's GitHub set-up and integration with third-party apps</td>
    </tr>
    <tr>
        <td>Open security vulnerabilities - ✨</td>
        <td>Number of unresolved vulnerabilities as identified by GHAS</td>
        <td>Adopt, Optimize, Sustain</td>
        <td><a href="https://docs.github.com/en/enterprise-cloud@latest/code-security/security-overview/viewing-security-insights-for-your-organization#autofix-suggestions">Organizational-level security insights</a></td>
    </tr>
    <tr>
        <td>CI success rate - ✨</td>
        <td>Number of successful CI runs inclusive of test automation / Number of attempted CI runs</td>
        <td>Adopt, Optimize, Sustain</td>
        <td>Calculation requires consideration of your organization's GitHub set-up and integration with third-party apps</td>
    </tr>
</table>


Form_Ungated_Contact

Tell us more about your needs

Wondering how GitHub can help your business?

We recommend to first focus on your developers’ adoption and engagement with Copilot. Then, harness developers’ improved productivity to pursue the engineering system improvements that matter most to your organization.

AI Background - Artificial Intelligence pillar - Dark 2

Resource Page for /artificial-intelligence/how-to-measure-github-copilot-impact

Glossary: Measuring the impact of GitHub Copilot

As your business grows, scaling your software teams becomes a necessity for continued growth.

In the simplest terms, growth means adding. Scaling, however, is much more than that. It is an equal parts strategy and process to enable efficient and sustainable growth. Scaling is a framework that enables your dev organization to add structure to key workflows, improve dev operations and evolve the software development process itself. It can empower large organizations to pursue ambitious growth, and to do so efficiently.

Many enterprise companies face difficulties associated with scaling, which can be challenging for larger companies working with more processes in place and with significantly bigger teams. Below are four key tactics to consider while scaling your development organization. 

## __1.  Process__

__Clearly Define Areas of Change__

It is vital to identify the areas that need to be transformed so that efforts are not wasted by uselessly adding processes and people in the name of growth. Look for areas that need improvement most, and stay focused on the efficiency of your teams and team structures from the start. For example, can you find ways to divide your development projects, thereby delegating certain functions to specific teams? Can you empower regular communication between your team leads to ensure that all teams are working towards the same goal? Can you focus on team structure and dynamics? Have the right people working well together in an environment that enables efficient problem-solving.

Remember that effective scaling doesn't mean that you continue blindly adding engineers. Be strategic in your approach. Scaling development teams involves knowing what types of skills and personalities to put together in a team to achieve the best sustainable outcome.

## __2.  People:__

__Understand Commonly Affected Functions__

Scaling up your organization will have far-reaching effects, often impacting teams beyond engineering. The following functions undergo changes when you scale the development org:

-   People

-   Processes

-   Culture

-   Communication

-   Projects

-   Code

-   Architecture

-   Budget

-   Testing

The impact of scaling impacts the organization as a whole, not solely the software teams, so this process is not only about engineers. Be strategic in your approach. Scaling your teams involves knowing what types of skills and personalities to put together in a team to achieve the best outcome, and accounting for all the functions which will be impacted in your organization.

## __3.  Timing:__

__Determine the Right Time to Grow__

The best strategies for scaling in software engineering are well-timed. The decision to scale your development organization depends on several key factors:

-   Your strategic goals

-   The state of your business

-   Your organizational needs

-   The overarching business strategy.

As a leader, you need to have the vision to analyze if it's the right time for scaling engineering teams. When you find yourself missing development timelines based on lack of resources on board or have a gap on the team tech skills that are required to deliver unique capabilities -- that's your cue that scaling is becoming a necessity.

## __4.  Tools:__

__Lean on GitHub for Scaling Simplified__

The GitHub Platform is the world's leading developer platform, trusted by 90% of the Fortune 100, and backed by Microsoft. It is the most trusted platform for Enterprise companies for good reason. With robust integration capabilities that seamlessly unite your development ecosystem, GitHub leverages the largest open-source community to help you scale your organization. Together, your teams can accelerate projects and build faster.

GitHub also leverages the largest open-source community to help you scale your organization. As projects and teams grow, the platform regularly reassesses and adapts to changing needs. When it comes to collaboration, version control, and community-building around software projects, the GitHub Platform has the power to transform the way your developers work, both individually and collectively.

<div class="embed-responsive embed-responsive-16by9">
  <iframe src="https://www.youtube.com/embed/Hpx4Zlu8ujk" width="640" height="375" frameborder="0" allowfullscreen></iframe>
</div>

Remember that your organization is unique, and your scaling strategy should be as well. While there may not be a one-size-fits-all approach to scaling development organizations in the Enterprise, it is vital to refer back to your product and business strategy as your North star to help you anchor to that which is most important. Scaling software teams in the enterprise can be challenging, however, with the right process, people, timing, and tools, it will help you drive massive impact and sustainable growth.

As your business grows, scaling your software teams becomes a necessity for continued growth. Many companies face difficulties with this, which can be especially challenging for larger companies with more processes in place and with significant teams to consider. Below are four key tactics to implement while scaling your development organization.  



Resource Page for /enterprise/scaling-made-easy

CO-GHG-CONTACT-FY23-10Oct-01-WW-Resources-Contact-Request/406214

Scaling Made Easy: Growing Your Developer Organization in the Enterprise  

![GHCopilotWS Header](//images.ctfassets.net/wfutmusr1t3h/47hzFdXO0PLAEO1cZXXDJK/847afb2e4e0c514524f41604d55dc687/512x160-GitHub-Copilot_Logo-Dark__1_.png)
GitHub Copilot is already being used by many people, but we conducted a GitHub Copilot workshop for those who want to learn how to use GitHub Copilot again and learn best practices. We are posting the video recording of the session and the slides so that more people can watch it.<br><br>
__Watch the video__<br><br>
__[Download slides](https://downloads.ctfassets.net/wfutmusr1t3h/1N24I5Rx5eRFqqq1DPNhGg/7670001e385b09c56dbc50feb6606e05/___240618_GitHub_Copilot_________.pdf)__<br>


Resource Page for /ghcopilotws2024june

GitHub Copilot Workshop

![GalaxyTokyo24 Cover Stage01](//images.ctfassets.net/wfutmusr1t3h/4fFlFcBXXmDL5hA9Ltii9S/e6c3763e7d72c44425bef0cf949df5d5/GalaxyTokyo24_Cover_Stage01.png)

GitHub Galaxy Tokyo is an annual event to share the latest GitHub Product update and share customer’s success stories and best practices.

Watch the videos

Download slides
<br>
午前の部：プロダクトセッション<br>
<a href="https://assets.ctfassets.net/wfutmusr1t3h/2nSV4tzO9xkLPf9F1UHtes/f6e80d1ebde4d640c5aa68b9ce3cfbae/1025-Daniel_240515GalaxyProductUpdate____v2__1_.pdf">GitHubプロダクトアップデートまとめ</a><br>
<a href="https://assets.ctfassets.net/wfutmusr1t3h/1ktVBTQbZzOWtSqNxhh1yr/072cf85ace0a418c4bd195a0d19eef47/1045-Nakase_2024GalaxyTokyo_HowGitHubIsUsingGitHub__1_.pdf">GitHubのためのGitHub</a><br>
<br>
午後の部：ビジネスセッション<br>
<a href="https://downloads.ctfassets.net/wfutmusr1t3h/3ZOkwodggcw91Jwmv123kn/3eee777944d6fc4dc77431d9da54b6c9/Galaxy24Tokyo_GitHubKeynote.pdf">GitHub基調講演</a>
<br>
<a href="https://assets.ctfassets.net/wfutmusr1t3h/3ER9o7YBcrA0gSnHlWhLMu/364c7334e57897c50fb8ffd1e7ea37ac/GitHub_Roadmap_Deck_-_FY24_-Jamie_Jones-.pdf">GitHub Roadmap</a>
<br>
<a href="https://assets.ctfassets.net/wfutmusr1t3h/63EyCiRcCYE9GNTHWmfS0T/d016ff600f871f05d783c55434aa62db/1545-_NTT_____________.pdf">NTTデータの生成AI活用の取り組みについて</a><br>
<a href="https://speakerdeck.com/cyberagentdevelopers/githubgalaxy_cyberagent">生成AIがもたらす変革～サイバーエージェントのGitHub Copilot活用戦略～</a><br>


GalaxyTokyo24 Cover Stage01

Resource Page for /galaxytokyo24archives

CO-GHG-IPVNT-FY24-05May-17-Post-event-LP-for-Galaxy-Tokyo-2024-7405

Galaxy Tokyo 2024 Archives

![RoadmapWebinar](//images.ctfassets.net/wfutmusr1t3h/7Mj0nuwLIpNTRt2TqZ0A21/48033add806ca13ba1b4c768de16fce8/RoadmapWebinar600x260.png)

GitHub [public roadmap](https://github.com/orgs/github/projects/4247/views/1) shows future development plans and feature release schedules.
The roadmap is useful to know in advance what GitHub will be doing in the future and what new features are planned for release, but it can be a bit confusing or difficult to understand the background of why it is being developed.
In this video series, we will introduce the GitHub roadmap in Japanese in a webinar format, and publish the videos as a video series on this website. We hope you will gain a deeper understanding of the roadmap and make better use of it.

GitHub Roadmap Webinar #1
<a href="https://assets.ctfassets.net/wfutmusr1t3h/2kIdcQcnYepIzzaCg0jlgj/05ab7a31d6c05548e7977dc7794174b3/GitHub_Roadmap_JP_2024Apr25.pdf">Download Slides</a>

<iframe width="560" height="315" src="https://www.youtube.com/embed/aGHA-U61CpM?si=soerb_dgg6EuFAl1" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>


RoadmapWebinar600x260

Resource Page for /github-roadmap-video-jp

/github-roadmap-video-jp 436290

GitHub Roadmap Webinar Video

Home > Bottom > Banner (Accelerate...)

Curate blazing fast developer environments and help your organization be more agile, secure, and efficient.

Home > Bottom > Card #1 (Codespaces)

Ship secure applications with a community-driven, developer-first approach.


Home > Bottom > Card #2 (Adv. Sec.)

Automate your software workflows with a powerful DevOps toolkit and built-in CI/CD.

Home > Bottom > Card #3 (Actions)

Safely publish and consume packages within your organization.

Home > Bottom > Card #4 (Packages)

Home > Feature > Banner > CTA

Home > Feature > Banner (Learning Pathways)

Bring the power of generative AI to engineering teams with GitHub Copilot. Learn how you can maximize developer velocity and innovation.


Copilot card

Stay one step ahead by shipping your software securely within GitHub: Identify and fix security issues directly in the developer flow.

Security Card

Learn why more than 90% of the Fortune 100 use GitHub—the leading developer platform compared to alternative solutions.

Why GitHub? Card

Become a GitHub expert in CI/CD, application security, governance, and AI-developer tools through expert-guided learning pathways with tips and insights from leading enterprise organizations.

Resource Page for /learn/build-like-the-leading-tech-innovators

GitHub Learning Pathways

Home > Final > Banner > CTA

Home > Final > Banner (Sales Team)

Home > Hero > CTA #1

Home > Hero > CTA #2

Set your business up for success with solutions to any number of common questions.

A checklist for AI-powered DevSecOps

Glossary: Measuring the impact of GitHub Copilot

Scaling Made Easy: Growing Your Developer Organization in the Enterprise

Browse by topic

Latest videos

GitHub Copilot Workshop

Galaxy Tokyo 2024 Archives

GitHub Roadmap Webinar Video

Accelerate innovation with the platform developers love

Codespaces

Advanced Security

Actions

Packages

Questions? Reach out to our sales team