Update Task to Use Relative Working Path #1844
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
The working directory is now optional because many commands no longer rely on a specified working directory.
tom-ludwig
requested review from
austincondiff,
bombardier200,
matthijseikelenboom and
thecoolwinter
thecoolwinter
approved these changes
Aug 16, 2024
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.
Description
CETask now saves the relative working path instead of the absolute path to accommodate variations between users’ environments. The working directory field will remain empty by default, eliminating the need for user input. This change simplifies task configuration via the JSON file, as only the task name and command are now required.
Related Issues
Checklist
Screenshots