Add branch evaluation support to module evaluation workflow and CLI #6
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
… keys for improved build performance
…namic keys for improved cache management and build performance
…weekly keys for improved cache sharing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Purpose: Enable evaluation of specific branches in FOLIO modules to support testing feature branches, development branches, and specific points in repository history without being limited to the default branch.
Approach: Extended the evaluation framework to accept an optional branch parameter throughout the stack:
branchfield toEvaluationConfigtype definitionGitUtils.cloneRepository()to accept optional branch parameter and use git's--branchflag--branch/-bCLI option to the evaluate command