Skip to main content

Self Onboarding

We are thrilled to have you join us!

This guide will help you configure your GitHub repository to be part of the Power Platform Open-Source Hub initiative.

Prerequisites​

To be able to onboard a repository into the initative you need to have the permission to add topics to it.

If you are not a maintainer of the repository, you can follow the Invitation to Join procedure and ask the maintainer(s) to complete the process.

Steps​

  1. Select in the list of the monitored topics the one(s) that best describe your repository - You can find the list of topics here.
  2. Go to your repository on GitHub.
  3. In the About section, click on the settings icon.
  4. In the Edit repository details dialog, add the selected topics to the Topics field.
  5. Click on Save changes.

That's it for the actions on your side!

Now we will just need to wait for a maximum of 24 hours for the repository to be added to the Power Platform Open-Source Hub initative and be visible on the website.

Repository metadata and curation​

The hub combines generated GitHub facts with human-reviewed curation:

  • Generated fields such as stars, topics, languages, releases, license, issues, and activity come from the daily pipeline.
  • Curated fields such as category, focus areas, audience, featured status, custom description, exclusion, and curated health are reviewed through files in Data\CuratedRepositories.
  • The daily bot can update generated files and the merged website data, but it does not create or rewrite curated overlays.

If your repository appears with the wrong category, focus area, audience, description, or health/featured badge, open a PR or issue requesting an overlay update. New taxonomy values should be requested with a clear description so maintainers can keep the vocabulary stable and useful for filtering.

Common overlay fields include:

  • customDescription for the human-written summary shown to users.
  • maintainerNotes for curation context that helps reviewers and future maintainers understand why an overlay exists or why a repository is excluded.

⚠️ maintainerNotes is included in the committed Data\GitHubRepositoriesDetails.json file, which is publicly visible. Keep this field to curation-relevant, publicly appropriate notes only.

  • exclude to intentionally remove a repository from the published catalog when maintainers have reviewed and approved that decision.

Curating a repository does not pin it in the generated catalog by itself. If a curated repository is not part of the sentinel list and later disappears from GitHub topic search results, the merge step fails loudly so maintainers can either restore discovery, remove the stale overlay, or intentionally add the repository as a sentinel.