Contribute

Solve issues

The simplest way to help is the point of the site: find an issue in a language you know and send a fix. Every closed issue makes the pile smaller, and a good first pull request is worth more to a maintainer than most people expect.

• Getting started walks through the four steps.
• The contribution guide covers how to be the contributor maintainers are glad to see.
• Finding issues shows how to narrow the catalog to what suits you.

Build SkillIssues

SkillIssues is open source and MIT licensed. Bug reports, feature ideas, documentation fixes, tests, accessibility improvements and pull requests are all welcome.

Before you open a pull request:

1. Read CONTRIBUTING.md. It explains how to run the project locally, which checks to run, and how branches and commits are named.
2. Read the Code of Conduct.
3. Open an issue first if the change is large, so we can agree on the approach before you spend time on it.

Changes are made through reviewed pull requests, and every merge to the main branch is deployed to production. That is why the project is strict about checks and about not swallowing errors.

Report a vulnerability privately, never in a public issue or pull request. See Security.

Other ways to help

• Suggest a repository that is missing.
• Report a bug or request a feature.
• Tell a friend who is looking for a first issue.