>_ FAQ

Answers to the most common questions about Pickssue and open source contribution in general.

About the Service

What is Pickssue?

Pickssue is a free tool that helps developers discover beginner-friendly GitHub issues across multiple repositories in one place. You add the repositories you care about, and the platform surfaces open issues labeled good first issue, help wanted, and similar tags — so you spend time contributing, not searching. Learn more on the About page.

Is Pickssue free to use?

Yes, completely free. There are no paid plans, no premium tiers, and no hidden costs. The platform is itself an open source project, so the code is publicly available for anyone to inspect, fork, or self-host.

Do I need to log in with GitHub to use the app?

No. You can browse issues without signing in. Anonymous usage is fully supported, though you will be subject to GitHub API rate limits, which means the number of repositories you can track at once is lower. Signing in with GitHub unlocks additional features including cross-device sync, browser notifications, and a higher API rate limit.

What data does Pickssue collect?

When you sign in with GitHub, Pickssue stores your repository list and preferences in a secure cloud database tied to your account. Your GitHub profile (languages, starred repos, contribution history) is analyzed to provide personalized recommendations and stored in the database. In anonymous mode, settings are saved only in your browser's localStorage. We do not share your data with third parties.

How does cross-device settings sync work?

When you are signed in with GitHub, your repository list and preferences are automatically saved to a secure cloud database. When you open the app on another device and sign in with the same account, your settings are restored automatically.

How do browser notifications work?

If you enable browser notifications in the Settings panel, the app will periodically check your tracked repositories for new beginner-friendly issues and send a browser notification when it finds any. You can configure how often the check runs — from every 30 minutes to several hours. Notifications require browser permission and only work while the app is open in a browser tab.

About Open Source Contribution

Can beginners with no professional experience contribute to open source?

Absolutely. Many of the most welcoming open source projects actively seek contributors who are just learning to code. A first contribution does not need to be a complex new feature — fixing a typo in documentation, improving an error message, or adding a test case are all genuinely valuable. Read our beginner's guide to learn the full process step by step.

How do I choose which project to contribute to?

Start with software you already use and care about. If you use a tool every day, you understand its purpose, which makes it easier to judge whether a change is correct and valuable. Also consider the project's maintainer responsiveness — look at how quickly recent pull requests were reviewed. A project with engaged maintainers is much more rewarding for new contributors than one where PRs sit open for months.

What should I do if my pull request is ignored?

Wait at least one to two weeks before following up, since maintainers are often volunteers managing their time across many responsibilities. If there is still no response after a polite follow-up comment, it is reasonable to move on to another project. Not every PR gets merged — sometimes the project is in maintenance mode, the issue was already resolved differently, or the approach does not fit the project's direction. It is not a reflection of your skill.

Can I contribute to open source if my English isn't strong?

Yes. Most open source communication happens in writing, which gives you time to look up words, use translation tools, and compose your thoughts carefully. Maintainers are generally patient with non-native speakers. Clear intent matters far more than perfect grammar. Code itself is a universal language — a well-written patch often speaks louder than any comment.

Does open source contribution help with getting a job?

Yes, significantly. Open source contributions create a public, verifiable portfolio of real-world work that goes far beyond what a resume can convey. Recruiters and engineering managers look at GitHub profiles when evaluating candidates. A history of merged pull requests demonstrates that you can read unfamiliar codebases, communicate with a team, follow conventions, and ship working code — skills that are difficult to prove any other way.

Are there ways to contribute to open source without writing code?

Many. Writing and improving documentation is one of the highest-impact contributions you can make — nearly every project needs it. You can also triage issues (reproducing bugs and asking for more information), translate content into other languages, design UI/UX improvements, answer questions in community forums or GitHub Discussions, or simply star and share projects you find valuable. The open source ecosystem depends on all of these contributions, not just code.

Still Have Questions?

Check out the full beginner's guide for a step-by-step walkthrough, or head straight to the issues page to start exploring open source opportunities.