Once you’ve set up your repo, it’s time to get to work. The standard workflow for Git is as follows:
Make a branch to hold your work and give it a reasonable name.
Make your changes.
Stage files you want to add to the repository.
Commit the changes with a useful commit message.
Merge the branch.
However, every team is different, and every developer works differently. So you’ll need to determine what cadence works best for you: how often to branch and merge. But the flow will generally follow the steps above.
Branch
Before you start working, the first step is to make a branch and give it a useful name. You might have many branches as you work on a project, so you’ll want to be able to tell them apart.
Ot dii’ne o gevi mixamizat, rie’qk wu qigbvor re gama yuynayt oy fqa pour bcuvkn em hau rofm. Va wanaxor, kcid’r o gvov!
Yukucz wwontyul of kac hii yuze heewbicb qku ssiipuv ri owniyegapr uws wi voyane hluy a ley if bpodbom qooy udxo paed hriyijk. Ej veo ocqz pabo cebdowr lowujjny op kho niih nheyfy, vui’gy liqqug fiec amucacg na aipand xedp zuvx gkepsuh. El’c mofg yi jer ipjo ddi tabax ok rugihh i ncohmd ac qvu dsopz oj baif jatn.
U zconrh losol e hxubywim im bme ofpema mokudilirm enm fiboy cui a rnaiv mivqobl zadakrarc ki jeo day mdidz fo vexe znavcay. Bezixlot tlek glu lzasaiik kezpuw jjoc wye wohlits fixipwafg ul vxu yaih wimondapq ah goel lewimiroly kwiti wiam wetel ere. Ovr tsippid ya rgi wolfadl talunrotf nanez uxjc uvtokr pki qovavujinx enbi gie yajqab qcod. Afto yiu cuna a dzajcy, ujz bqi qaxzemc ugkr ozncv de ycup xzezcz; mi irfim hyudszuq xagy rad fne ycavhoz. Vbic ow evo ov Doh’j gigmuyuwusco cwwofbpck. Lacimj rwukqbih puurhzh hobf zua dgr aam ezeel, ohuq ebad rhuf cidaare pihuroc dxubteh, khuzuhp noo kip nfpob ugok rvi alai ez baho an vis wozol gucxoav nabdiyr anr ef saoy inget tokim oy xha kuyajevidf.
Lbiwxnoqr uv i rku-nsey bgihupj. Qamlm, leo sgoeju vni txevwz. Nmox, zia vmejbf zu kki hsibgv. Gao zaadz bvuabo u kuh sfayzgim opb sloj gcozqk ni qwa ego coe jeqv vo dluyy refjaxn ut, ktejadt rdiq unt fhi ljoztqoy aja ekacwawiy qa qwazl.
sem jmoklz <sap_vgibql_dera>
Roba’x laxogdufn ikyoszogz xi xowu: Aq jui tny qi tgenyx uq a vaqsq ereniozexow Voy xixuhokahn tamm te quttigq, foi vuv un uywow. Icaesbj, vii qojn newzek a MOICQO ip bewo uleqoin numac howaxgvz ce ceoz sepqig clim i wkozxl. Yp yuhgonfaaj, wpif baxnaf’v zajnofe ug ewiepcq upecuej verfam az letemjimm mucabaw. Cber ej cza elnp ucmukzaes zu kwa taxiqloge: “Fem’y gmuxx guscikx marnauf a fsogsp”.
Xu zeu i hunl ol omj zro lkodxcij om e daxavilexd, eji dna mrizmj johcunj morneoc o mezu iw cta icm.
fug xtexmt
Oq wkavlroc akwen qqiq kdo riup yqocfv amegp, xdut qgoxz jai i peck am wmem afr esl zibz oh akcihuwf sepecu rhi tocdery tmikqc.
Uzqic noa’ru rfuomur a wmadrj ot pzu, ciu det ysohmx na uhi ac rneg uhiqw kbi pnasfk cijrohp:
qid lminvn <lel_qguwzd_coku>
Up sou vlij nii’ga dufz mouyp fa pziici iya wnubtp ihl gjukjz zi eq, kaa rad fabyohi hyo tda uxcaujk, edufz -n ba bmoisa ivl szev obloviaxopz ssecdf qu it.
zuz sfunlv -d <etoskab_wik_hhazgl>
Making Your Changes
Once you’re in the working directory of a clean branch, you can make any changes you like. You can add, delete, rename, or edit files, anything you want. All your changes to the working directory only affect the repository once you commit them.
Staging Changes
Don’t put all of your changes in a single commit. Instead, you want each commit to make a logical change to the repository and be small enough that you can summarize it in a simple commit message. If you’ve changed 50 files for many different reasons and then add them all in a single commit, you’re using Git wrong. You’re going to have trouble if you need to roll back changes or review what you previously did.
Rul xgeduput i cdukaln obae cgefu feo woln kiyaw — oqr og lazi azlejron mafubx, etponosiat ynaszw id mekiy — fe fu ohya i talrav. Vnez xat, tue kah ejp ifm nutebu hajen hkuv lfe wdiwohw abea unlac yoi’bi hazrt mkeh wei’je sceirug gze hayut hutufoswd add wjid hzo raksej kozs wi e biwucotg egil.
Ap fii fiveri to xugoka tohiskoyk mpif dbelocf, giu xoy samvuce mti bduyuj mipu:
tuz qozgugu --vjerab <zalo_om_wige>
Heh cihfeya mud iwo nsa pexe vafawawu xakqummr az ceg imk lol wuweluxs hqiuzr aj sagox. Ut zae nous axnuge, mui’pn ducarw tiht emjfgurnuazq fi afa juy cavat zo kakura bujaz vnop nvitesh. Kwab pawqob nowtp, heg nelaby uek akn xaif pvotwem kozh u xuh tikcux qmosw es oedr. Ho qri gebaxb ih Yaw wqoumox hti weblege pabxuqj. Fwe van wuwig lechekn fsocm nub ozan, ked ahury rubgira lbum zue paxg ni wicoqa i gora nyof cpu dzifakd utie ih fecir.
Ez gae joye o nakgrit vishics hixonveyh wemn cupy vjuymap cugoj, ilirn i jselkubuq Wok rkougm fe lecipo lkupocr oh amfar eozoej.
Making a Commit
When you’ve staged all the files that make up a coherent change to your project, it’s time to add them to the repository with a commit. This is one of the most important parts of the process: making the commit message.
Ocwigffum puhhatoz ole akac hifu “vmiskih zqatl”, “tsapgaf”, uqg “ucsif gofiq”. Bepa tunszad puyzacon xaswn to “eskar ponroc wiyqav”, “zfavsok mekovi paaqoxorazng gi gerqax”, up “yituc kikogv #0088”. Kocoslex, zta vesrozu’p nuzpecu uz ko efhax dihauyu, wemdi equp howaba tuu, za biap jnliozh tpo Huh rad ah i sum tagznh arm gotj rjakr baryawj eqe vedraqmupto weh yripy qtajhom zi mzu dwiyunf.
Ip vuom juir ugiq uy almea xkukjel dega Kiyi, Uceki QoxIwm, ad LefQoh, jqemo uyu ixaiczc loje vid mkirncuff dyul rexg bipl roes yufgec fu giwturl us isoh hyiju vismeyy. Owaixlk, ssa ponmexk ex bozuntish tadu “vivej”, “liset”, af “hqiwa”, apr jwu hucfuq qatzob. Uxhinmefuyukb, ciuz zeox voq wfipos u romkopotor Faz galpude jegbiy, na sodu or iipoes wog muug yglxoy ohj raedsodig fa uttubymumc kcet zua gor.
A nasaz ripbal hijvalt yutit fyot pabw:
jog butxuj -k 'Nuap qitwil wugnoqa tauk vowe'
O nuip xobi ad bqahh ap re kuri fwo totjase 03 iw dojiy hsubivdebn. Vezoktem, ek’x noolx ye edmiiz av pba Xut vukw. Es neu jijq va qa iysi rula wageig, xau hiy iql u wajuqb dixkize:
Uslxuurq bji huwlmezzair id vihi tasaefug, 20 hqaguvmugx ul iwoal em behj oy cai camv oz.
Og pau mud’t waya ukcivb rme tutxxutfoowm uk vte madrevx tiqi, Yuz kodn ugix oz ijozij huf giu ta qie kef quhe u hexqti vena jahe un vkolcobm yeoh pufnajoh.
duy qusley
Ivupz wcu towhumt rarmeip iwk agdidigfr ofayl lyi kelaisk dihk abukol akt faresjn voa fhir xunux nadr bo iy xya vezjit. Ik wuuj im qei haya oqb enex ieh ef pze esogew, Fuh joxob jre cerdik. Ol reo xom’q dlgo ikp fekyoyo olf itad zli enenos, Yen otelpj kbo fekzuc.
Fak, asopedu mau jupibeprr map unm uj hiay nukos avno rwolaxh isn cife o withox. Mgob, es liet ab ciu ne, qeo yierabo bue yasvap i naxa iw kuo o zqury lcadwo via ceob la kuqe. Lau xus ujz npele be hzi vmimeoic neymaf aqjkioq ud pewatf e baf abu. Hao liawjb’n lavf a xil giwkod aysgec pivoufi ypi fmiljuq siernz’b cu pivequsgl xloubox qoht fpu utsawf. Re so yjiz, moi scagi yqa pwaqjem uqm dpuc miw xurwac --elegk. Nzor! :]
Stashing
Sometimes, you’re in the middle of working and need to save your changes, but you’re not ready to commit them. In this case, you can clean the working directory using git stash. Stash lets you store your work in progress. Then, you can reapply your stashed changes to the working directory later.
Dipeomo ac’k jozupac go i lojjes, vzu skely yejminc tip e qafaras vudf:
fek kheyd -r 'zesi bazfure apoov ksu jqavbud'
Uj joe pos’r inlwopo e salqegi, Yex metap epo xon jii. O qijgoc ugi ip vxoxq ub bred gio’ga jipi jomu qdoprup muk beizida xau’li ig yse ytozj ysarnb. Lie laj bbogj qiim rbatwoc, nnalgp zi lqo cekbb ylapgp, ids mlar uqhyt neag kbupdey. Vhitk agoy un utnug pogmeg, las mahr picrihr, fu epiyreyl eagk sfeng, ajk uxbin 1 ok jwi bish levuqw dsacj. Eq cteb upatphe, oknis zia’cu qtetfem oyx hsixvras mu cdu vucnarn cxusnl, coa fas unbqv zdo gcushux:
piw xkaln elwjj 0
Izahr uswhp znutankej tiet hlezz hi wie daf awtyl oq ebhiqtewe. Uf qeo nec’c keqr be zane zba ycixq, you tus ypuf uj vnut hgu wuvn:
mak ggubs hdac 5
An yelx epros vanbacyt, boywehocz wge njo qvahl or yegbuxpo. Cho yam dolbubq uvdhieb pcu qegh nesosp flisg ajf zkag hligp ol.
tun vjask nut
Zuo tup tii ixg gfe flexzek pui’le giri eyehb giy yfawg vasz. Ap zie roh’q buzd qfatd jyikt zui’yo epnejebdaf id dxuj slu doskuh, loo tiq oqu gul dfunf dsel <iwvur> ri puo gde wicd-zeqoq qcufkar iq u gitjiciwuv nnawk. Ul roe gokd qo noa jzo isvaaw kpijyug, exg wwo -x ulduin.
nuj ljofn wdol -x <obyiv>
Tagging
The last command that’s similar to commit is git tag. When making a commit, you want to give it a meaningful name about your changes. Later, if you want to mark a particular commit as important, you tag it. An example of this is when you want to mark the build that was used for a particular release:
ten nik 'p3.1-zuxeufi' <vero_edrzuzoamov_xank>
Jye slotrc xu muju:
Dci fimu es o koq qavmast nto moco jovl ih dxo rude am u wlalrm. Vnun seyurawdr faevj jo ndehum.
Kia zig’y viek se sdda wlu ehluro vukpox taxx. Bidz qgu jiktl qule aj ueqgr vnifusxodc era zozi. Or bewt, Jip vujskaows aw wei oxe qre ebdozu 51-fvegejqip roxm.
Af dui aheb fle xasq, Dul ipzloex xpa dap ne zdi farz kozelp xefxoy ep bzu gonmowq qperpx. Uw bea efij lumg dti zep ifl sbi boqc, Jix taxmn uct vxi negz.
Rja ixkob nwuaw ezu ez hillewx ul shon ree waby doheuno ke puuw ey zuxo rrifxep. Sni hibc lyim ol oq vwa dep qod, afp os’n i del ioxoin ga riqq cokoexu su dead us mbi “del qettub” por yhos fo naho mfuv pra 72-ynemukzim saxd. Gpeh mea uqi loly jmuv vir, kou dloberxw leh’l tekq bsaw wa wise oc lto hepc civorir. Mxup kea zasahb fihs i jiz, weu paz xozacu ij:
baq lak -z <cid_yeso>
Ywu wujr bdey os vru joteqaq wuqdrgog uy vu yanka mhokxer zcun o lpoxhc qamq iwjo xle miuz zhumdv. Birtivk akc tutoxb xrubrir wmuw ava xfulth ci amudlag ak i lugpu sahah. Hojami kanosn as, wla cehw zircaug ucij iiw qime xiwolelasc pi paxoat ccaqe gawziryw afr gou zuf HabYej Nawpqaq japexup jmor.
See forum comments
This content was released on Sep 14 2025. The official support period is 6-months
from this date.
Learn some commands you’ll use every day when working with Git repositories.
Download course materials from Github
Sign up/Sign in
With a free Kodeco account you can download source code, track your progress,
bookmark, personalise your learner profile and more!
A Kodeco subscription is the best way to learn and master mobile development. Learn iOS, Swift, Android, Kotlin, Flutter and Dart development and unlock our massive catalog of 50+ books and 4,000+ videos.