BUILD-10724 migrate only when S3 is forced#51
Merged
julien-carsique-sonarsource merged 1 commit intomasterfrom Mar 25, 2026
Merged
Conversation
98fc655 to
0ab9153
Compare
SonarQube reviewer guide
|
SonarQube reviewer guide
|
bwalsh434
approved these changes
Mar 24, 2026
Contributor
bwalsh434
left a comment
There was a problem hiding this comment.
Awesome! In theory, ths is must more efficient in number of operations executed 👌
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
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.




Summary
Change the default for
import-github-cachefrom alwaystrueto context-aware:truewhen the S3 backend was explicitly forced viabackend: s3input orCACHE_BACKEND=s3env var — the intentional GitHub→S3 migration scenario.falsewhen the S3 backend was auto-detected (private/internal repository) — these repositories have always used S3 and have no GitHub cache entries to migrate.Changes
action.yml:cache-backendstep now emitsbackend-source: forced|auto;import-modestep uses it as the smart default.README.md: updated inputs table and Migration Mode section to document the new default and resolution order.Note on future default change
When S3 becomes the default backend for all repositories (including public), the auto-detection case will also need to check repository visibility (
public→true,private→false). That change is deferred to when the default is actually switched.Test coverage