How to Make Your Issues Requests Come True
Tags: opensource, beginners, github, tutorials
Published: 2023-02-22 16:43:35

---
title: How to Make Your Issues Requests Come True
published: true
date: 2023-02-22 04:16:39 UTC
tags: #opensource #beginners #github #tutorials 

series: Chrissy’s Open Source Survival Guide
canonical_url: https://chrissycodes.hashnode.dev/how-to-make-your-issues-requests-come-true
---

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8vr2q7dtwg4q5yjf8ytg.jpeg)

### You made it! 😊

Oh hey, welcome back! 😊 I see that your first contribution was merged congratulations! Youre making waves in the open source world! 🎉 What, you want to do another one? Alright! 😊 Now before you start PR-bombing other projects, theres another thing you must know: how to raise an issue. Remember how Jiminy Cricket in _Pinocchio_ told us as kids that our wishes will come true regardless of who we are if we wish upon a star? Well, issues are like that, wishes that we share with the stars (or in this case, the open sources project leaders) and hope they happen. What makes raising issues even greater is that they are pretty easy to do, so take your magic wand (or computer's mouse in the case) and sit tight because were about to go on a magic carpet ride.

![Aladdin & Jasmine fly on the magic carpet while a group of storks surround them](https://media.giphy.com/media/WUu9EGdSEImJy/giphy.gif)

### No issues = No Open Source Projects

- Like the fairies in Neverland, issues are the energy of open source projects. Without the input and ideas of users, these projects lose their magic and may struggle to survive. By making feature requests, you play a critical role in shaping the direction and success of the project. For example, when I was scrolling through EddieHub's Linkfree website and had an idea: what if there was a chart comparing Linkfree and Linktree? I mean, who doesn't love a good chart? So, I shared my idea with the project leaders, and they were on board faster than Fairy Godmother saying "Bibibty Boppity Boo." What made it even better is that other members of the community joined in to help make the feature request a reality. Right now, it's still a work in progress, and I'm eagerly awaiting the day when that chart goes live and blows people's minds.

### How to do the Raise an issue spell

Contrary to popular belief, raising an issue is not that hard. All it takes are the following steps:

1. Click on the repository of your choice.

2. Click on the **New Issue** button: This button is usually located near the top of the repository page and may be labeled "New Issue", "Feature", Bug report", or something similar.

3. Fill out the issue form of your choice & click on **Submit New Issue**

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1677036889249/a6ac7ea2-84c5-45c7-bbea-6f621117ad9e.png)

Now that you know how to make wishes, I mean issues. Its time to make sure that the genies, aka the project leaders, grant them. But no worries, Ive gotten some tips thatll help you faster than the Sorting Hat from Hogwarts.

![Mini Dr. Strange beckons you to come in the portal he conjures](https://media.giphy.com/media/l0HlxJMw7rkPTN8sg/giphy.gif)

### Dos & Donts

**Do's**

1. **Do** use a descriptive title in the title section: It helps other contributors and project leaders understand your suggestion.

2. **Do** follow the checklist and guidelines provided: Some projects have specific rules in place to make it easier for leaders to see how your suggestion fits into the project. Its kind of like how a feather wont levitate unless you say the Leviosa spell correctly (shout out to Harry Potter).

3. **Do** post a link to your pull request in the conversation section: Other contributors and the leaders might want to give feedback on your PR to ensure that it follows the issue you raised, so adding that link makes things easier. Think of it as a page number in the Table of Contents of your spell book.

**Don'ts**

1. **Don't** use the same issue template for each suggestion you have: Each issue is unique, and using the same template can make it harder for leaders to understand what you're suggesting.

2. **Don't** forget to reference it in your pull request: If you don't reference the issue in your pull request, it might be hard for the leaders to connect the two.

3. **Don't** pressure the leaders and other contributors to respond right away: Remember that open source projects are run by volunteers, so it's important to be patient and respectful. Nobody likes a pushy issue wizard.

## Conclusion

Congratulations youre officially an issue wizard! 🎊🎉 Remember, without you and your suggestions, open source projects would be closed. If you want to learn more ways to be an open sourcerer, be sure to follow me on [Hashnode](https://chrissycodes.hashnode.dev/) and my other socials via [LinkFree](https://linkfree.eddiehub.io/CBID2). Now go forth and make some magic! 😊

![Night sky with fireworks booming behind the phrase "The End" written in white](https://media.giphy.com/media/l4FAPaGGeB7D1LfIA/giphy.gif)

### Credits

Concept Art Love GIF by [Disney](https://media.giphy.com/media/WUu9EGdSEImJy/giphy.gif)

Korean Drama Goodbye GIF by [The Swoon](https://media.giphy.com/media/w610hKOSa1KosUa95Y/giphy.gif)

Let's Go GIF by [Marvel Studios](https://media.giphy.com/media/l0HlxJMw7rkPTN8sg/giphy.gif)

Magic Book by [Dollar Gill](https://unsplash.com/photos/0V7_N62zZcU?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)

The End Airplane Movie GIF by [Film editor](https://media.giphy.com/media/l4FAPaGGeB7D1LfIA/giphy.gif)