How to create a README file

How to create README file for your git code

What is a README?

A well formatted text file that is used to document important information about your GIT project for any user who starts to use it for the first time.

Sample README.md file

Generally there is just 1 README.md file per project. But if needed it can also be created for each module in a project.

How to create a README?

Most commonly used format for README files are markdown language. That’s why you see a file extension ‘.md’. markdown language can be thought similar to HTML.

Steps to create a README.md:

When a new git project is created a blank markdown file README.md file is created automatically.

  1. Open the README.md file using a text editor. You can use text editor like Notepad, notepad++, Sublime etc.
  2. Edit the file using markdown language. Learn markdown language syntax from here.
  3. Commit the file to git to see the preview . Alternatively, you can use any editor like  Atom, Emacs, Sublime TextVim to create and preview the file.

You can also directly open the file in Git UI and edit it using the markdown language. Git UI also has an option to Preview the file .

That’s It !

Sample README File:

Find below the template of a README.md file written using markdown language syntax.

Copy the below to any text editor to begin creating your README.md file.

# Header H1
Header H1 is used to display the Project heading. 

## Sub Topic Headings H2
Sub Topic Headings H2 is used for sub sections like Configurations, Authors etc.

````
pip install boto
````

The above formatting is used to create a box which can display code or command in a well formatted manner.


## Usage

Below is another example of displaying
````python
import csv

with open("sample.csv","r") as csvinput: # read input csv file
    reader = csv.reader(csvinput) # create a reader
    for row in reader:
        print(row[0])
````

 

OUTPUT README :

The output of sample README.md after committing the file in git looks like below.

Markdown Syntax

As git README.md file is created using markdown language, learning some basic markdown syntax can be very useful to style your README.md file.

Learn syntax for the following most commonly used elements in the git README.md

  • Text formatting
  • List creation
  • Code block creation
  • Table creation

Text Formatting:

Bold: To create text as bold enclose it in double stars or double underscore.

Italic :  To create text as bold enclose it in single star or single underscore.

Syntax:

**bold** OR __bold__

*Italic* OR _Italic_

Output:

bold OR bold
Italic OR Italic

Lists:

Ordered lists: Markdown syntax for creating numbered list is just by putting numbers in front of each row.

Syntax:

1. One
2. Two
3. Three

Output:

  1. One
  2. Two
  3. Three

Unordered lists: Bulleted lists can be created using star or dashes.

Syntax 1:

* Star is used to create a bullet list item
* Item 2

Output:

  • Star is used to create a bullet list item
  • Item 2

Syntax 2:

- You can also use Dashes instead of stars
- Parent Item
 - Item 1
 - Item 2

Output:

  • You can also use Dashes instead of stars
  • Parent Item
  • Item 1
  • Item 2

Code Blocks:

Backticks are used to create code blocks .For inline code wrap it in single backticks.

Syntax:

`variable a = 20`

Output:

variable a = 20

For multiline code block : Use spaces for indentation & use 4 backticks for code blocks without indentation:

Syntax:

if(IndentationRequired)
print(“use 4 spaces”)

Output:

    if(IndentationRequired) 
        print(“use 4 spaces”)

Syntax:

````
if(IndentationNotRequired)
print(“use 4 spaces”)
````

Output:

if(IndentationNotRequired) 
print(“use 4 spaces”)

Create Tables:

Tables are created using dashes and pipes. Dashes are used to underline the headers and pipes are used to separate the columns.Check the example below.

Syntax:

Column 1|Column 2
--------------|--------------
Row element| Row element

Output:

Column 1Column 2
Row elementRow element

Summary

In this article, we learnt what is readme and we also learnt how to create a readme file for your project.
I hope you liked it !


Git Merge Vs Rebase

When to use git merge ?

Use it as a default scenario when you don’t want to bother about the commit history and want to avoid problems, anyways it comes as default with git pull.

When to use git rebase ?


Use it to make your commit history look more clear and consistent.

Can be used for temporary local branches(like feature branches).

You can use git rebase -i(interactive) for rewriting the local commit histories into a neat one before you push it to the remote repository.

Difference between Merge and Rebase – When to use what


Git MergeGit Rebase
git merge apply all the unique commits from one branch to the other in one commitgit rebase takes all the unique commits from both the branches and applies them one by one
merge does not rewrite any commit history but just add one new onerebase rewrites the commit history but doesn’t create extra commit to merge

Summary

In this tutorial we looked into the difference between git merge and git rebase and when to use what.
Hope you liked it!