mirror of
https://github.com/Frooodle/Stirling-PDF.git
synced 2025-12-18 20:04:17 +01:00
af2e418129
# Description of Changes This pull request simplifies the workflow logic for the `docker-compose-tests` job in `.github/workflows/build.yml`. ### What was changed - Removed the extended conditional logic that depended on the results of the `test-build-docker-images` job. - Updated the `needs` configuration so that `docker-compose-tests` depends solely on `files-changed`. ### Why the change was made The previous logic attempted to optimize execution flow but introduced unnecessary complexity and conditional branches. By simplifying the workflow: - Job relationships become easier to understand and maintain. - The workflow executes more predictably. - The dependency graph becomes clearer, reducing potential misfires caused by mixed job states. --- ## Checklist ### General - [x] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [x] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [x] I have performed a self-review of my own code - [x] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md#6-testing) for more details. |
||
|---|---|---|
| .. | ||
| ai_pr_title_review.yml | ||
| auto-labelerV2.yml | ||
| build.yml | ||
| check_properties.yml | ||
| codeql.yml-disabled | ||
| dependency-review.yml | ||
| licenses-update.yml | ||
| manage-label.yml | ||
| multiOSReleases.yml | ||
| PR-Demo-cleanup.yml | ||
| PR-Demo-Comment-with-react.yml | ||
| pre_commit.yml | ||
| push-docker.yml | ||
| releaseArtifacts.yml | ||
| scorecards.yml | ||
| stale.yml | ||
| swagger.yml | ||
| sync_files.yml | ||
| testdriver.yml | ||