feat: set usage arguments and flags as environment variables for toml tasks #4159
Conversation
This file contains 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
…s environment variables when running toml tasks
|
I think this is a solid change! One thing I believe it doesn't handle, and I don't know how important it is—or how tough it would be to add, would be using templates with env vars: |
|
Yes, unfortunately, it does not handle templates with environment variables right now... However, it could certainly be an interesting addition for the future |
jdx
pushed a commit
that referenced
this pull request
Feb 8, 2025
### 🚀 Features - **(registry)** add jd by [@risu729](https://github.com/risu729) in [#4318](#4318) - **(registry)** add jc by [@risu729](https://github.com/risu729) in [#4317](#4317) - **(registry)** Add qsv cli by [@vjda](https://github.com/vjda) in [#4334](#4334) - add support for idiomatic go.mod file by [@roele](https://github.com/roele) in [#4312](#4312) - add -g short version for unuse cmd by [@kimle](https://github.com/kimle) in [#4330](#4330) - add git remote task provider by [@acesyde](https://github.com/acesyde) in [#4233](#4233) - set usage arguments and flags as environment variables for toml tasks by [@gturi](https://github.com/gturi) in [#4159](#4159) ### 🐛 Bug Fixes - **(aqua)** trim prefix before comparing versions by [@risu729](https://github.com/risu729) in [#4340](#4340) - wrong config file type for rust-toolchain.toml files by [@roele](https://github.com/roele) in [#4321](#4321) ### 🚜 Refactor - **(registry)** use aqua for yq by [@scop](https://github.com/scop) in [#4326](#4326) ### 📚 Documentation - **(schema)** fix description of task.dir default by [@risu729](https://github.com/risu729) in [#4324](#4324) - Add PowerShell example by [@jahanson](https://github.com/jahanson) in [#3857](#3857) - Include "A Mise guide for Swift developers" by [@pepicrft](https://github.com/pepicrft) in [#4329](#4329) - Update documentation for core tools by [@hverlin](https://github.com/hverlin) in [#4341](#4341) - Update vitepress to fix search by [@hverlin](https://github.com/hverlin) in [#4342](#4342) ### Chore - **(bun.lock)** migrate bun lockfiles to text-based by [@risu729](https://github.com/risu729) in [#4319](#4319) ### New Contributors - @vjda made their first contribution in [#4334](#4334) - @kimle made their first contribution in [#4330](#4330) - @pepicrft made their first contribution in [#4329](#4329) - @jahanson made their first contribution in [#3857](#3857)
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.
Fixes #4070
@jdx I have tested it locally and everything seems to work fine, but before merging the PR I would like to have your opinion if everything seems ok. After that, I would like to add some e2e tests, but I do not know whether it is better to add them to e2e/tasks/test_task_run_toml, e2e/tasks/test_task_vars or to create a new test file just for this feature. Where do you think it is best to add them?