Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify --init filename/extension #2008

Open
HeCorr opened this issue Jan 21, 2025 · 1 comment · May be fixed by #2018
Open

Specify --init filename/extension #2008

HeCorr opened this issue Jan 21, 2025 · 1 comment · May be fixed by #2018
Assignees
Labels
area: ui Changes related to the UI of Task.

Comments

@HeCorr
Copy link
Contributor

HeCorr commented Jan 21, 2025

Summary

I personally much prefer the .yaml extension over .yml, but it doesn't seem like I'm able to specify which one to use when initializing a Taskfile with --init, so I'm always forced to rename the file afterwards.

Suggestion

Either:

  • add the -e, --extension flags that let me specify which file extension to use (either .yaml or .yml), or
  • repurpose the existing -t, --taskfile flags to specify the target filename if --init is also present
    • maybe also support a wildcard for the filename? i.e. task -i -t *.yaml ➡️ Taskfile.yaml
@task-bot task-bot added the state: needs triage Waiting to be triaged by a maintainer. label Jan 21, 2025
@HeCorr
Copy link
Contributor Author

HeCorr commented Jan 21, 2025

I'm willing to give this a shot, please assign me.

@andreynering andreynering added area: ui Changes related to the UI of Task. and removed state: needs triage Waiting to be triaged by a maintainer. labels Jan 22, 2025
@HeCorr HeCorr linked a pull request Jan 25, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ui Changes related to the UI of Task.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants