refactor: always run build service check if repo is found #1088
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.
Summary
This PR ensures that the
build_service_check
is always executed when a repository is found, regardless of whether thebuild_as_code_check
detects an automatic deployment. This is especially important for ecosystems like Python, where the build and deployment steps are often separated and may use different tools or workflows. By always running the check, we avoid missing critical build data needed for rebuilding packages.Description of changes
Previously, if the
build_as_code_check
identified an automatic deployment, thebuild_service_check
could be skipped. However, for build from source, it is important to collect all build commands. Skipping thebuild_service_check
in such cases omits valuable information about the build process.This change ensures that:
build_service_check
runs whenever a repository is detected.