Add force build option #53
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
August 15, 2025 14:05
This change introduces a new `force_build` input to the `ios-selfhosted-build.yml` workflow. This allows users to bypass the change detection mechanism and force a build to run, regardless of whether relevant code changes have been detected. This is particularly useful for: - Manually triggering a build for a specific commit. - Re-running a failed build without making new code changes. - Ensuring a build is always produced for a given branch or tag. When `force_build` is set to `true`: - The `universal-detect-changes-and-generate-changelog` action is skipped. - Build-related steps (Fastlane, IPA/dSYM upload) are executed unconditionally. - The changelog for the build is set to "Forced build". - The latest build commit SHA is not saved or cached, as it's not based on detected changes.
The `ios-selfhosted-build.yml` workflow was incorrectly evaluating the `force_build` input as a string literal `'true'` or `'false'`. This commit changes the comparison to treat `force_build` as a boolean value directly. - Previously, `inputs.force_build` was compared against the string `'true'`. - Now, `inputs.force_build` is compared against the boolean `true`. This ensures that the `force_build` input is correctly interpreted, allowing the workflow to behave as expected when a forced build is triggered.
The `if` condition `inputs.force_build != true` was removed from the "Detect changes and get changelog" step in the `ios-selfhosted-build.yml` workflow. This ensures that the change detection and changelog generation action always executes, regardless of whether a build is being forced. This is crucial for: - Maintaining consistent and accurate changelogs for releases. - Ensuring that change detection logic is always applied, even in scenarios where a build is manually triggered or forced. This change prevents potential inconsistencies in changelog generation when `force_build` is true.
viktorvrchlavsky
approved these changes
Sep 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a
force_buildinput to theios-selfhosted-build.ymlworkflow, enabling builds to proceed even if change detection would normally skip them. It also adjusts subsequent steps to respect this new input and provides a specific changelog for forced builds.Key Features
force_buildboolean input to the workflow.force_buildis true, bypassing change detection.force_buildis active.Workflow Input
force_buildbooleanfalse