This will give you the experience and understanding of how to report your webpack build stats to us. The rest of this documentation will assume you have done this, and will outline the additional steps needed to set you the other projects you have in your repository.
One packtracker.io project for every webpack project
The first step in this process will be to create a project on packtracker.io for every webpack project you wish to track. For example, if you have 3 different projects in your repository, you need to have 3 separate projects on packtracker.io.
Multiple projects set up on packtracker.io
Once you have these projects set up, you will need to retrieve the project token for each project you wish to report on.
By default, we use the repository name for the project name. In most cases this is a sane default. However, in the case of a mono-repository configuration, you need to rename them to match your internal project structure.
Rename each project to match your internal project structure.
Then, you will configure each additional webpack build (per project) using the project tokens of each project. You have done this once before with your initial project, you should simply need to repeat these steps.
For illustration, in my example repository, I'm passing unique PT_PROJECT_TOKEN environment variables to each build, using independent secrets configured in GitHub.
Additionally, you may also need to specify each project's root directory if you are using our automated stat reporter (like GitHub Actions or the CircleCI Orb).
Once you have correctly set up reporting for each project using the project tokens, you are all done.
If you have done everything correctly, you should see multiple projects report their GitHub Checks successfully
Reporting for both the test-cra3-mono project and the test-next-mono project in a single repository.
You can see an example configuration and pull request here: