To maintain code integrity and ensure that our committed changes include all generated files, we need to implement a check for uncommitted changes after the build process in our pipeline. This check will use the "has-changes" GitHub Action to detect any uncommitted changes in the repository and exit the pipeline with a failure status if changes are found.
This is necessary because some info will be removed at random when using Stencil's dev mode (e.g.: documentation of CSS variables). To prevent this we want to ensure that our committed changes contain all generated files
Acceptance Criteria
[ ] The pipeline configuration includes an extra step after the build step has finished
[ ] The extra steps correctly detects uncommitted changes that were generated by the build step, indicating that some generated files were not updated correctly in the local environment
[ ] If uncommitted changes are found, the pipeline fails with an appropriate error message.
[ ] The pipeline successfully completes without errors if there are no uncommitted changes.
Description
To maintain code integrity and ensure that our committed changes include all generated files, we need to implement a check for uncommitted changes after the build process in our pipeline. This check will use the "has-changes" GitHub Action to detect any uncommitted changes in the repository and exit the pipeline with a failure status if changes are found.
This is necessary because some info will be removed at random when using Stencil's dev mode (e.g.: documentation of CSS variables). To prevent this we want to ensure that our committed changes contain all generated files
Acceptance Criteria
buildstep, indicating that some generated files were not updated correctly in the local environmentFurther informations