### What needs to get done Create a test workflow that builds the docs for each of our applications when a PR changes any files under `docs/common`. This workflow should: 1. Check out the application's main branch 2. Check out the craft-parts current branch 3. Set up the application docs environment 4. Install the current branch's craft-parts into the docs environment (making sure that we're then using the correct version of `craft-parts-docs` 5. Build the docs for the application ### Why it needs to get done Changes in `docs/common` fairly frequently cause downstream application issues. This will reduce this or at least warn us before merge when it happens. cc @medubelko