5 Tricks to Create an Impressive GitHub Repository 🤩🤯
Tags: productivity, career, github, git
Published: 2022-05-08 06:18:32

Want to hook users up to your **GitHub repository**? Want **GitHub** to promote your **repository**? Want users to come back to your **repository** again, and again?

If you answered **YES** to all the questions, you have come to the right place, my disciple. In this article, we will be going over how to create an impressive **GitHub repository** that hooks users!

![wow](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/j8cjhqw8xnj7uui6dxva.gif)

## 1. Add Description (with Emojis & Link)

This is the **lowest hanging fruit** in creating an impressive **GitHub repository**. You can just add a short description of the **repository** to heighten its appeal. Make sure to throw in some **emojis** too 😉.

You also get **extra brownie points** 🎂 for adding **relevant links** too!

![description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/k0ympesq5brqei2y65l2.PNG)

You can update the **description** and the **link** from the top right **settings icon**

![configure](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/1y7gmi0frosb4v9orq9x.PNG)

## 2. Add Tags

Adding **tags** is the next and most crucial step in this article. It not only makes it easier for **GitHub** to promote the **repository** but also makes it **look much more professional**!

![tags](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/y8lz07theh46hh232kr0.PNG)

**Tag** related settings are also available in the **repository configuration** shown in the previous step

## 3. Add License

No point denying it, this is the most boring step, but essential for **fair use of the repository**. Moreover, it also shows up in the info tab, so just get it done with.

![info](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ohrs3w6lfh31qp4y9da2.PNG)

To add a **License**, create a file called `LICENSE` at the **root of the project**.

## 4. Add Readme

The **ReadMe** is the first thing a visitor sees when they visit the **repository**, so taking some time to create a polished **repository** is crucial. It should describe **what problem the code solves**, **how to set it up**, and any **other relevant information**.

![readme](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/p6gm8yun1civf4a83pd9.PNG)

There is always some way to make the **ReadMe** engaging. Even if you don't have much to write about the **repository** itself. Take the example of a **repository** containing **coding problem solutions**. You can easily **list out the problems** in the **ReadMe** and **link to the solutions**.

![coding-problems-readme](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/bfgk9ydfeo763ddnx859.PNG)

To add a **ReadMe**, create a `ReadMe.md` file at the **root of the project**.

## 5. Use Descriptive Commit Messages

Using descriptive **commit messages** might look like a chore, but it too helps in taking the appeal of the repository higher. Make sure the **commit message** is explanatory.

There are various schools of **commit message** structures, any of which is acceptable. I personally like the following one:

```bash
<type>[optional scope]: <description>
```

If you want to dive deeper into how it is structured, check out [this article](https://www.conventionalcommits.org/en/v1.0.0-beta.2/)

![commits](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/1mraa63nqyn8qqenfyap.PNG)

## 6. BONUS: Use Multiple Languages

Using **multiple languages** in your repository is a great way to grab the user's attention, but this is highly context-dependent. You should **NOT** use **multiple languages** only to increase the appeal, but only if it is required.

![multiple-languages](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7f59km7zor6kanq4ztay.PNG)

Even if you falter in this department, as long as you implement the other tricks, **you are completely covered**!

## Repositories used

{% github https://github.com/ruppysuppy/Daily-Coding-Problem-Solutions no-readme %}

{% github https://github.com/ruppysuppy/Crypto-Crowdfund no-readme %}

{% github https://github.com/ruppysuppy/SmartsApp no-readme %}

{% github https://github.com/mui/material-ui no-readme %}

Finding **personal finance** too intimidating? Checkout my **Instagram** to become a [**Dollar Ninja**](https://www.instagram.com/the.dollar.ninja/)

# Thanks for reading

Need a **Top Rated Front-End Development Freelancer** to chop away your development woes? Contact me on [Upwork](https://www.upwork.com/o/profiles/users/~01c12e516ee1d35044/)

Want to see what I am working on? Check out my [Personal Website](https://tapajyoti-bose.vercel.app) and [GitHub](https://github.com/ruppysuppy)

Want to connect? Reach out to me on [LinkedIn](https://www.linkedin.com/in/tapajyoti-bose/)

I am a freelancer who will start off as a **Digital Nomad** in mid-2022. Want to catch the journey? Follow me on [Instagram](https://www.instagram.com/tapajyotib/)

Follow my blogs for **Weekly new Tidbits** on [Dev](https://dev.to/ruppysuppy)

**FAQ**

These are a few commonly asked questions I get. So, I hope this **FAQ** section solves your issues.

1. **I am a beginner, how should I learn Front-End Web Dev?**
   Look into the following articles:

    1. [Front End Development Roadmap](https://dev.to/ruppysuppy/front-end-developer-roadmap-zero-to-hero-4pkf)
    2. [Front End Project Ideas](https://dev.to/ruppysuppy/5-projects-to-master-front-end-development-57p)