generated from actions/typescript-action
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Feature: use Github working directory #160
Comments
joergi
added a commit
to joergi/file-existence-action
that referenced
this issue
Mar 19, 2024
joergi
added a commit
to joergi/file-existence-action
that referenced
this issue
Mar 19, 2024
joergi
added a commit
to joergi/file-existence-action
that referenced
this issue
Mar 19, 2024
joergi
added a commit
to joergi/file-existence-action
that referenced
this issue
Mar 19, 2024
joergi
added a commit
to joergi/file-existence-action
that referenced
this issue
Mar 19, 2024
joergi
added a commit
to joergi/file-existence-action
that referenced
this issue
Mar 19, 2024
joergi
added a commit
to joergi/file-existence-action
that referenced
this issue
Mar 19, 2024
joergi
added a commit
to joergi/file-existence-action
that referenced
this issue
Mar 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In GitHub Actions you can use working directory:
documentation
This is an example, how it should look like
but later in the file existence check, I have to repeat the working directory for the file existence check
These examples are from here
there should be a possibility to say: use working_dir yes or no.
I would love to see the example working like this:
Readme.md should look like this:
files
ignore_case
true
follow_symbolic_links
true
fail
false
working_dir
false
It would make sense to have the working_dir set as a standard to
true
but this would let all existing file checks fail, that's why I would set it default to false.I was trying to look if I could implement it myself, but I was missing the skills to do it in TypeScript
this could also maybe closes issue #150
The text was updated successfully, but these errors were encountered: