GitHub Copilot Rollout - Sessions 1
GitHub Copilot Rollout - Sessions 1
Rollout
February 2024
Today’s Agenda
01 Context Setting
03 Demo
• Microsoft is funding the use of GitHub Copilot licenses for all the vendors having a valid vendor (v-) ID.
• Accenture has experimented internally, and we have seen up to 50% productivity gains (commits) from our
internal CIO study of 400 engineers using GitHub CoPilot (Nov 2023)
• Independent external pilot programs have proven that GitHub Copilot supports faster completion times,
conserves developers’ mental energy, helps them focus on more satisfying work, and ultimately find
more fun in the coding they do.
• Presently the CoPilot adoption in the account is negligible, and we are commencing a drive to increase the
adoption and usage among our developers.
Potential Use Cases for GitHub CoPilot adoption
Onboarding Efficiency/Speed Quality Improvement
Limitations:
1. The responses may not always be completely correct. The developers still need to validate and test
for the response generated by GitHub copilot.
2. It is not very efficient in writing test cases and covering all possible scenarios but can provide a
good starting point with some standard test cases to start with.
• Once the request is submitted, it will take from 1 to 2 hours for approval. GitHub username by default is your v-id_microsoft (eg: v-name_microsoft)
Pre-requisites for GitHub Copilot in VS Code
1. Install the Extension-
• For VS Code: Install Copilot extension (includes Copilot Chat)
• For Visual Studio: Install Copilot extension, Install Copilot Chat extension
3 Document Code
Some use-cases for GitHub Copilot- VS Code
Get Code Suggestions
1 Generate Test Cases 2
3 Document Code
Sample Task achieved with GitHub Copilot
1. GitHub Copilot was able to transform a nested object to remove unwanted
keys and create a desired output object.
Sample Task achieved with GitHub Copilot
2. Modify the developed code to a class-based implementation.