Master Git & GitHub | Part 2 | Fundamentals

preview_player
Показать описание
Instructor in this video: Harsh Sharma

Socials:
Peace ✌️

#gitandgithub #github #git #backenddeveloper #webdevelopment #codingtutorials
Рекомендации по теме
Комментарии
Автор

Summary of this Video ;
git reset --soft HEAD~1
=> Move the HEAD pointer to the previous commit, keep the changes staged.

git reset --mixed HEAD~1
=> Move the HEAD pointer to the previous commit and unstages the changes but keep changes in working directory.

git reset --hard HEAD~1
=> Move the HEAD pointer to the previous commit and discard the changes completely in staging area and working directory.


Like if you want ❤❤

TagdaCoder
Автор

Part -2 complete not skipped on single minutes. Love the playlist

abishpradhan
Автор

go with this video guys ....it's just simple and he cover only that things which we will use in our daily project work,

raghavmanish
Автор

u nailed it sir and your voice mashallah love it

uniquetrends
Автор

thanku harsh sir ....now i have complete the second video on the same day of first video again sir

raghavmanish
Автор

ye wala session maja aaya har bnda code push krna hi sikha rha tha hats off

yubrajkhatri
Автор

In the context of GitHub and version control systems, CRLF and LF refer to different types of line endings used in text files:

CRLF: Stands for Carriage Return (CR, \r) followed by a Line Feed (LF, \n). This is the line ending sequence used by Windows. It’s essentially telling the text editor to return to the start of the line (CR) and then move down to the next line (LF).
LF: Stands for Line Feed (\n), which is the line ending sequence used by Unix-based systems like Linux and macOS. It simply moves the cursor down to the next line.
When collaborating on code that will be used across different operating systems, inconsistent line endings can cause issues. For example, if a file with CRLF line endings from a Windows system is pushed to a repository, and a Linux user pulls the file, their editor might display the CR characters as extra characters at the end of each line, or it might not interpret the line breaks correctly.

To prevent these issues, Git can be configured to automatically convert CRLF to LF when committing code, and vice versa when checking out code. This ensures that the repository maintains a consistent line ending style, while developers can work with their native line endings locally.

GitHub recommends setting up a .gitattributes file in your repository to manage line endings. This file allows you to define rules for how Git should handle line endings for different files, ensuring consistency across all contributors’ environments1.

You can also use the git config command to set the core.autocrlf option, which controls how Git converts line endings:

git config --global core.autocrlf true: On Windows, this converts LF to CRLF when checking out code and CRLF to LF when committing.
git config --global core.autocrlf input: On Unix-based systems, this ensures that line endings are LF on commit and does not convert them on checkout.
git config --global core.autocrlf false: This disables automatic conversion, preserving line endings as-is.
These settings help maintain consistency and prevent issues related to line endings when multiple collaborators are working on a project using different operating systems

talhaanwar
Автор

smooth!!!! things what we actually need in Rl

D-kq
Автор

How do i go forward after going backwards a few too many steps?

hussainabbas
Автор

Very big fan of Harsh Bhaiya and Akarsh Bhaiya

MohammadRamzan-jmgb
Автор

Sir ye understandable ke liye to samaj aya bahut jyada

But akdom real project Mein kese use karna hain sir... Ak bar batayiyega next video main please 🙏🏻 🙏🏻 🙏🏻 🙏🏻 🙏🏻
🙏🏻🙏🏻❤️

bhaskarartwork
Автор

😎 Proud to be a part of Backend Series by Harsh Bhaiya❤

codezaura
Автор

Part-2 completed also we can use git lens extension for tracking the version and to get back to previous we can also use this cmd - git checkout id of the commited file instead of git reset cmd

abhinav
Автор

Mashallah boht acha samjhaya, Thanks ❤
Jb git log --oneline chalatay hain toh all commit ki ID milti ha. Hum kese kisi particulay commit ki tarha ka code kr saktay hain ID ko use kr k.
Matlab k is particulay commit pr kese ja saktay hain ID ko use kr k ❓❓❔❔

raza_dev
Автор

asay krnay say toh hum "git reset --hard HEAD~2" apny code kay 2 version peechay jatay hain agr ye krnay kay baad hum apnay code kay uss verison mein janna chahay jo hum nay delete kr diya hai toh uss kay?

Motivate-x-yourself
Автор

Sheryians ko bhi ab samajh aya hai short vdos pr regular upload se reach badhti hai. Warna CWH ko mock chl rha tha ki 10 min mein thodi concept padhaya jata. Deep mein Jane ke liye long form jaruri hai pr growth short form mein jyada hai, nahin? Anyway I'm still a big fan of harsh sir ❤

YogeshMore-vvef
Автор

Sir bohat achi video lagti hy apki apny teaching kaha say sehki aur bohat mazay may samj lag jata hay sab kuch. Love from Pakistan.

syedusmankhalid
Автор

Its a very good thing that you upload videos on regular ba

armoury..handla.
Автор

Bhaiya backend series mai real world projects add kar do na project based learning k liye.

rajaryan
Автор

this is the best video every I seen on youtube

AdilAli-mtlm
welcome to shbcf.ru