This makes it easier for you to know how popular the project is. You can also search for a repository based on how many stars and forks the project has. You can also combine multiple search queries to further narrow down the search. For example to find all repositories where freecodecamp is listed in the topic, our search will be: freecodecamp in:topic You use this to find if a certain phrase or word is labeled in the topics. If we want to find repositories where the term freecodecamp is included in the README, our search will be: freecodecamp in:readme. You use this to search through a README of a file for a certain phrase. If you want to find repositories with a ceratin description, for example repositories where the term "freeCodeCamp" is included in the descriptionm, our search will be: freecodecamp in:description In this case, you can use the command Data Science in:name which will list repositories with Data Science in the repository name. Let's say you are looking for resources to learn more about Data Science. This makes it possible to search "inside" what you are looking for.
#GITHUB FIND FILE BY NAME HOW TO#
Let's look at some ways you can narrow down your search: How to Find by Name, Description/READMEĪ thing to note when you search by Name and description of the README file is that your search phrase should begin with the in qualifier. is:issue is:open no:assignee - This shows all open issues that have not yet been assigned to a person.īy default, to make a search you will type the repository name in the search bar and voilà! You get some search results.īut the chances of you landing on the exact repo you intended are very low.no:label type:issue is:open - This lists all open issues that are not labeled.But if you want to find issues that are not tracked, this search query will list those projects for you. no:milestone type:issue is:open - Many times, projects are tracked with milestones.no:project type:issue is:open - This will list all open issues that are not assigned to a specific project.is:issue is:open label:up-for-grabs - This lists open issues that are ready to be worked on if you have the necessary skills.is:issue is:open label:starter - This lists all open issues from across GitHub that are labeled starter.is:issue is:open label:"good first issue" - This will list all open issues with the label good first issue, meaning it is good for place for beginners to get started.is:issue is:open label:good-first-bug - This lists projects with open issues labeled good-first-bug, to attract contributors to work on them.is:issue is:open label:first-timers-only - This lists all open issues that welcome first-timer contributions.is:issue is:open label:easy - This will list all open issues that are labeled easy.is:issue is:open label:beginner - This particular query will list all projects with issues that are open and labeled beginner.Here are some tricks you can use to easily find reliable answers: One of the most common ways of finding projects to contribute to is by searching through issues and related PRs. How to Search Issues and Pull Requests on GitHub Listed below are some of the tricks that might help you out when you are using GitHub.
Most maintainers tend to label their projects with issues, which makes it easier for contributors to find suitable projects. How do you get started? Which keywords should you use to find the correct results?
It's not any different with GitHub – to find detailed info you can utilize common filter, sort, and searching techniques to easily find specific issues and pull requests of a given project.Įven though you have multiple resources listed on the internet for different projects, the main problem comes in when you want to do a search by yourself. In order to find detailed information about something on the internet, you need to have the correct searching skills. You'll learn how to search through:Īnd more. In this article we are going to take a look at different techniques you can use to correctly search GitHub. Just like mastering Google search skills is essential for any regular internet user, I believe it's also essential for developers to learn how to effectively search GitHub. Now the question isn't what you use these version control systems for, but how you are using them. But as a developer, chances are that you'll interacting with GitHub or Gitlab on a daily basis. Let's agree on one thing: unlike Google, searching GitHub is not easy. But I always wanted to find a way around this problem – a way I could search for and track projects that were right for my skill set. When I was a beginner to open-source contributions, one of my greatest challenge was finding the correct projects/issues to work on.įor the longest time I relied on resources curated by different writers on the internet (which were good, by the way).
0 kommentar(er)
