JPMorgan Chase Software Engineering Virtual Experience
Software engineering task :
making a patch file
Setting up your dev environment for the program!
Disclaimer
● This guide is only for those who did the setup locally on their machines.
● For those using REPL (from module 1), please use this guide instead
Setting up your dev environment for the program!
Prerequisites
● Set up should have been done. This means,your server and client
applications should have been running with no problems without introducing
any changes to the code yet. You can verify this if you get a similar result to
any of the following slides that include a picture of the server and client app
running together
● You should have made the necessary changes to the client script to make the
application output correct values
Setting up your dev environment for the program!
Intro: What is a patch file
● You should know by now that git is a way for developers to manage code in a
project especially if there’s other developers collaborating in that project too.
● A git patch file is just a file that you can apply to a repository to get the
changes / modifications / additions another developer did on his / her machine
onto your local machine. This isn’t the only way to do that ofcourse but this is
a viable method for a head/lead developer to check your code first before
merging it into the repository’s main/master branch.
Setting up your dev environment for the program!
How to make a patch file
● Fire up a terminal, enter the repository via the terminal you opened (via the cd
<repo_name_here> aka change directory command) and do the following commands
(one line, one command)
git add -A
git config user.email "<your_email_address>"
git config user.name "<your_name>"
git commit -m 'Create Patch File'
git format-patch -1 HEAD
note: make sure you use your personal email address and your real name
Setting up your dev environment for the program!
How to make a patch file
The final command, i.e. git format-patch -1 HEAD, should produce the .patch file
you’d want to submit to complete this module. It will be located in the directory
where you executed the command.
Setting up your dev environment for the program!
How to make a patch file
● That’s how it would look like if you executed the commands properly
● note: ls will only work for Linux and Mac environments. For Windows, use dir
to list the files in the current directory so you can verify that you created the
patch file
Setting up your dev environment for the program!
And you’re done!
● Submit the patch file on the right module page

More Related Content

ODP
Contributing to Upstream Open Source Projects
PDF
How, When, and Why to Patch a Module
PDF
XPDDS17: Contributing to Xen
PDF
Contributing to open source using Git
PDF
SFO15-TR2: Upstreaming 101
PDF
Howto Test A Patch And Make A Difference!
PDF
Software maintenance PyConUK 2016
KEY
Tweakers Anonymous
Contributing to Upstream Open Source Projects
How, When, and Why to Patch a Module
XPDDS17: Contributing to Xen
Contributing to open source using Git
SFO15-TR2: Upstreaming 101
Howto Test A Patch And Make A Difference!
Software maintenance PyConUK 2016
Tweakers Anonymous

Similar to create_patch_file_v3a.pdf (20)

PPTX
Take control. write a plugin. part II
PDF
Assign, commit, and review - A developer’s guide to OpenStack contribution-20...
PDF
Getting Git Right
PDF
Assign, Commit, and Review
PPTX
Intro to Github
ODP
U boot source clean up project how-to
PDF
From hello world to goodbye code
PPT
CSE 390 Lecture 9 - Version Control with GIT
PDF
Hg for bioinformatics, second part
PDF
Getting Started with (Distributed) Version Control
PDF
Collaborative development with git
PPTX
Basics of Open Source Contribution - WWCodeMobile
PPTX
Constantly Contributing Pretty Patches FLCD
PDF
Git & Code review
PDF
Intro to Git, GitHub, and Devpost
PDF
Git best practices 2016
PDF
Jr devsurvivalguide
PPT
391Lecture0909 Vision control of git.ppt
KEY
Tweakers Anonymous
PDF
Git Makes Me Angry Inside
Take control. write a plugin. part II
Assign, commit, and review - A developer’s guide to OpenStack contribution-20...
Getting Git Right
Assign, Commit, and Review
Intro to Github
U boot source clean up project how-to
From hello world to goodbye code
CSE 390 Lecture 9 - Version Control with GIT
Hg for bioinformatics, second part
Getting Started with (Distributed) Version Control
Collaborative development with git
Basics of Open Source Contribution - WWCodeMobile
Constantly Contributing Pretty Patches FLCD
Git & Code review
Intro to Git, GitHub, and Devpost
Git best practices 2016
Jr devsurvivalguide
391Lecture0909 Vision control of git.ppt
Tweakers Anonymous
Git Makes Me Angry Inside
Ad

Recently uploaded (20)

PPTX
Computer Architecture Input Output Memory.pptx
PPTX
CHAPTER IV. MAN AND BIOSPHERE AND ITS TOTALITY.pptx
PPTX
ELIAS-SEZIURE AND EPilepsy semmioan session.pptx
PDF
Paper A Mock Exam 9_ Attempt review.pdf.
PPTX
202450812 BayCHI UCSC-SV 20250812 v17.pptx
PDF
BP 704 T. NOVEL DRUG DELIVERY SYSTEMS (UNIT 1)
PDF
HVAC Specification 2024 according to central public works department
PPTX
Unit 4 Computer Architecture Multicore Processor.pptx
PDF
AI-driven educational solutions for real-life interventions in the Philippine...
PPTX
A powerpoint presentation on the Revised K-10 Science Shaping Paper
DOCX
Cambridge-Practice-Tests-for-IELTS-12.docx
PDF
Vision Prelims GS PYQ Analysis 2011-2022 www.upscpdf.com.pdf
PPTX
Share_Module_2_Power_conflict_and_negotiation.pptx
PPTX
20th Century Theater, Methods, History.pptx
PPTX
B.Sc. DS Unit 2 Software Engineering.pptx
PDF
Uderstanding digital marketing and marketing stratergie for engaging the digi...
PDF
Hazard Identification & Risk Assessment .pdf
PDF
IGGE1 Understanding the Self1234567891011
PDF
Empowerment Technology for Senior High School Guide
PPTX
History, Philosophy and sociology of education (1).pptx
Computer Architecture Input Output Memory.pptx
CHAPTER IV. MAN AND BIOSPHERE AND ITS TOTALITY.pptx
ELIAS-SEZIURE AND EPilepsy semmioan session.pptx
Paper A Mock Exam 9_ Attempt review.pdf.
202450812 BayCHI UCSC-SV 20250812 v17.pptx
BP 704 T. NOVEL DRUG DELIVERY SYSTEMS (UNIT 1)
HVAC Specification 2024 according to central public works department
Unit 4 Computer Architecture Multicore Processor.pptx
AI-driven educational solutions for real-life interventions in the Philippine...
A powerpoint presentation on the Revised K-10 Science Shaping Paper
Cambridge-Practice-Tests-for-IELTS-12.docx
Vision Prelims GS PYQ Analysis 2011-2022 www.upscpdf.com.pdf
Share_Module_2_Power_conflict_and_negotiation.pptx
20th Century Theater, Methods, History.pptx
B.Sc. DS Unit 2 Software Engineering.pptx
Uderstanding digital marketing and marketing stratergie for engaging the digi...
Hazard Identification & Risk Assessment .pdf
IGGE1 Understanding the Self1234567891011
Empowerment Technology for Senior High School Guide
History, Philosophy and sociology of education (1).pptx
Ad

create_patch_file_v3a.pdf

  • 1. JPMorgan Chase Software Engineering Virtual Experience Software engineering task : making a patch file
  • 2. Setting up your dev environment for the program! Disclaimer ● This guide is only for those who did the setup locally on their machines. ● For those using REPL (from module 1), please use this guide instead
  • 3. Setting up your dev environment for the program! Prerequisites ● Set up should have been done. This means,your server and client applications should have been running with no problems without introducing any changes to the code yet. You can verify this if you get a similar result to any of the following slides that include a picture of the server and client app running together ● You should have made the necessary changes to the client script to make the application output correct values
  • 4. Setting up your dev environment for the program! Intro: What is a patch file ● You should know by now that git is a way for developers to manage code in a project especially if there’s other developers collaborating in that project too. ● A git patch file is just a file that you can apply to a repository to get the changes / modifications / additions another developer did on his / her machine onto your local machine. This isn’t the only way to do that ofcourse but this is a viable method for a head/lead developer to check your code first before merging it into the repository’s main/master branch.
  • 5. Setting up your dev environment for the program! How to make a patch file ● Fire up a terminal, enter the repository via the terminal you opened (via the cd <repo_name_here> aka change directory command) and do the following commands (one line, one command) git add -A git config user.email "<your_email_address>" git config user.name "<your_name>" git commit -m 'Create Patch File' git format-patch -1 HEAD note: make sure you use your personal email address and your real name
  • 6. Setting up your dev environment for the program! How to make a patch file The final command, i.e. git format-patch -1 HEAD, should produce the .patch file you’d want to submit to complete this module. It will be located in the directory where you executed the command.
  • 7. Setting up your dev environment for the program! How to make a patch file ● That’s how it would look like if you executed the commands properly ● note: ls will only work for Linux and Mac environments. For Windows, use dir to list the files in the current directory so you can verify that you created the patch file
  • 8. Setting up your dev environment for the program! And you’re done! ● Submit the patch file on the right module page