Git and GitHub guide

Part 3
Contribution To Open Source

Zero To Mastery
by Andrei Negoie
Lection 148. We start from 05:41 minutes ( follow these steps)
1

3. git clone https://github.com/antonykidis/start-here-guidelines.git

4.Cd into start-here-guidelines.
2 5.ls
CODE_OF_CONDUCT.md CONTRIBUTORS.md 'Get Started.md' LICENSE README.md

6.Type start code . (for VS Code should open the entire folder)
7.Branch out git checkout -b test
8. Add your name to the list of contributors
9. Save all CTRL+S
10. git add .
11. git commit -m“test“
12. git push origin test
13. git push
14. go back to https://github.com
15. See a notification
16. Finish a pull request as
appears in the video.

test test
A different way adding yourself to CONTRIBUTORS.MD I've decided
We could skip the previous page and do the following to add myself this way

* Another way adding yourself to a CONTRIBUTORS.md list would be editing it straight

on a start-here-guidlines GitHub repository.
Dmitry's
1. Go to the forked repo https://github.com/antonykidis/start-here-guidelines way
2. At your left hand side click the CONTRIBUTORS.md file.
3. Click Edit (pencil icon)
4. Add your name to the very end of the contributors list (using the mark down syntax)
5. Commit changes. 3

2
1

6. You will recieve a new Pul Request notification.

7. Finish this procedure by clicking Compare and Pull request button.
8. Administrators will accept this pull request and merge it into master.

Congratulations on adding yourself as a new contributor!

 ...Meanwhile somewhere in the cosmos
One of the administrators have merged
our pull request into the master.
We've been added to a CONTRIBUTORS.md list.

this
Pull request
Is now merged
Into master
Adding
My name
To contributors
list

master master
 After adding myself to a contriburors list via GitHub website, I finally decided
to repeat these steps, but this time by cloning a repository, adding myself to the
Contributors list, and pushing it back to a gitHub (as it apears in the original video)

I can say that I've edited the contributor's list two times so far.
Dmitry 1. By editing it on a GitHub website.
2. By cloning a repo, modifying a contributors list, and pushing it back to a GitHub
3. This caused the notification to appear once again.

Okay I have a new pull

request notification.
But I don't need it because
my name is already
In the contributors' list
Hmmm... Dmitry
Is there any way to get rid of it?
It's a good question...
1

We could try to delete the commit like this

1. Go to a forked repo https://github.com/zero-to-mastery/start-here-guidelines

2. Click commits link.
2. Locate your commit.
3. Copy the commit ID 2
4. Go to terminal.
5. type git push origin +9ad5cf5^:master

+ Specify what destination ref to update with what source object.

The format of a <refspec> parameter is an optional plus +, followed by the
source object <src>, followed by a colon :, followed by the destination ref <dst>

^ HEAD^ means the first parent of the tip of the current branch.
6. You will get the following output
7. Go back to commits (gitHub) and check if it's been deleted.
8. Repeat the previous steps again to delete another
desired commints you want.

9. Once every commits is been removed, the pull request

Notification will no longer appear on the GitHub website.

10. You can then delete a remote branch like this:

11. Type git push origin --delete fix
In my case fix was the name of the branch

As you can see i've successfully deleted

Commits and a remote branches.
We now left with only one commit, and
one master branch on our forked repository.
 Additional Information
You could encounter with some unexpected things while working on the Git and GitHub section of the course.

They are as follows:

1. What if we mistakenly entered a bad commit's message. How to fix that without pushing a whole new files into the GitHub again?
2. Your bash terminal showed a weird vim editor window (only for win. Users) How to use it?
●

Solution: How to Edit a bad commit message.

1. Go to a forked repository, open commits link, and find a commit you want to fix.
2. Copy a commit's ID to a clipboard
3. Open terminal window.
4. Use this command. git revert fd8f4fe
5. hit ENTER.
6. The vim editor window will appear.
7. The yellow text will represent a commit message.
`
8. Hit insert button on your keyboard. This will allow you to manipulate a text.(use arrows to navigate)
9. Delete the yellow text, and write hello world (for example)
10.Press ESC button to exit the text editor mode.
10.Hold down SHIFT+ : this will bring you to the vim script mode(check the left bottom corner, you will put commands there)
11. Type wq (w= write) (q=quit saving changes) and hit ENTER
12. You will recieve the following output, with updated commit message
13. type git push to apply changes

SHIFT+:

Vim editor
Step 14.Go back to GitHub and see the changes

We've just successfully changed the

commit's message.
But the files are left the same.
Great. It works.

Dmitry
 A few things to keep in mind before we continue

➲ Sometimes you will merge a master

branch to one of your other branches, just
to keep things up to date.

➲ You will probably encounter this VIM editor

window again and again, especially if you
on windows.

➲ Take a few minutes to read a short

Introduction to VIM (in the next section), to
avoid unpredictable situations, and other
questions you might encounter with.

➲ Usially gitbash will automatically open

~/.git/commit_EDITMSG file

➲ You can edit this file using notepad.

But gitbash does it in a more intuitive way
without exiting the shell (all in one
solution)

➲ No need to learn VIM, simply learn the

basic commands.
A short introduction to VIM
Http://vim-adventures.com

https://brigade.engineering/crap-wrong-mode-9021375c2826
http://learnvimscriptthehardway.stevelosh.com
The End of part 3