Hi, if you are reading this is because you pretty likely want to participate in the development of this API and curious about how to start.

You are in cpp-sc2 core project, but actually, we have more repositories you can contribute to:

• codegen - type IDs codegeneration utility;
• commandcenter - original version of CommandCenter bot with integrated cpp-sc2;
• docker-sc2 - dockerized StarCraft II Linux client;
• scrubber - scrubs type ids from a game client.
• blank-bot - starter bot for StarCraft II with integrated cpp-sc2.

What can I do?

• Search for other issues tagged with good first issue or help wanted tag.
• Suggest new features.
• Vote for existing issues (issues with highest number of reactions are likely to be fixed first).
• Fix // FIXME: comments in the code.
• Improve the documentation of the API.
• Add/Fix/Improve tutorials.
• Add/Fix/Improve new bot examples.
• Add/Fix/Improve tests.
• Help to test latest changes.
• Support this project on Boosty (preferred) or Patreon. Support of the project allows to make releases more often and implement nice new features for developers.

If you have any suggestions, feel free to comment on this thread, or chat me over Discord (the #cpp channel).

What should I know before the start?

Code guidelines
We do our best to conform to the Google C++ Style Guide with the exception that we use four space tabs instead of two space tabs.

Commit guidelines
We follow the semantic versioning approach, this is important so your PR will appear on the Changelog 🎉 ! I guess you expect recognition and we will give it to you.
See standard-version for commit guidelines.

The list of supported commit message prefixes:

• feat - a new feature or API improvements;
• fix - a bugfix;
• perf - performance improvements;
• refactor - code refactoring;
• test - functional or unit tests;
• build - build system improvements, also includes CI improvements;
• docs - documentation improvements;
• chore - routine task, e.g. create new release (doesn't appear in the changelog);
• style - fix code style, no functional changes (doesn't appear in the changelog.

Before PR

• Keep the PR small as possible and one single topic for each.
• Write good commit message: describe what was the problem and why the changes required.
• Consider implementing a test.