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

Expose --force(-all) flag as variable so it can be acted upon #1412

Closed
hans-d opened this issue Nov 28, 2023 · 1 comment · Fixed by #1434
Closed

Expose --force(-all) flag as variable so it can be acted upon #1412

hans-d opened this issue Nov 28, 2023 · 1 comment · Fixed by #1434
Labels
area: variables Changes related to variables. good first issue Issues that are good for first-time contributors to pick up.

Comments

@hans-d
Copy link

hans-d commented Nov 28, 2023

the --force/--force-all flag is now used for status checks, eg https://taskfile.dev/usage/#by-fingerprinting-locally-generated-files-and-their-sources

Some tasks that are run could benefit from this flag as well to force a refresh/rebuild, eg do-something {{if eq .CLI_FORCE 1}} --force{{end}}

@task-bot task-bot added the state: needs triage Waiting to be triaged by a maintainer. label Nov 28, 2023
@andreynering andreynering added type: feature A new feature or functionality. good first issue Issues that are good for first-time contributors to pick up. area: variables Changes related to variables. and removed state: needs triage Waiting to be triaged by a maintainer. labels Nov 28, 2023
@andreynering
Copy link
Member

I think this makes sense. Pull requests are welcome.

@pd93 pd93 removed the type: feature A new feature or functionality. label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: variables Changes related to variables. good first issue Issues that are good for first-time contributors to pick up.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants