Use GitHub variable to define OFT file patterns #190
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
sophokles73
added
enhancement
sophokles73
force-pushed
the
use_repo_variable
branch
12 times, most recently
from
7f5c5e3 to
bb7e658
Compare
sophokles73
force-pushed
the
use_repo_variable
branch
from
bb7e658 to
e60e381
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Use UP_SPEC_OPEN_FAST_TRACE_FILE_PATTERNS variable to look up the file patterns to use for running OFT.
Also adapted the run-oft Action to dynamically determine, if a JRE needs to be installed.