You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many people were surprised by the change that hidden files are no longer uploaded unless hidden-files: true is set. Even explicitly named files are not uploaded. This is confusing, and encourages people to turn off the safety feature completely.
If I name a hidden file, it should be uploaded regardless of the setting.
To make an analogy: ls ignores hidden files. ls -a shows them all. ls .gitignore shows me the hidden .gitignore file even without the -a flag.
I agree with the sentiment of the issue, In case it gets decided that the current behaviour is intended (or while discussion about it is on-going), I would suggest that explicitly specified filepaths that end up being ignored should lead to an error or big fat warning telling you about it. There is currently no difference in behaviour between
so in almost every case I can think of, the former is a configuration mistake that should throw up some flags. It currently makes no sense to specify a path with a leading dot without also setting include-hidden-files: true.
What happened?
Many people were surprised by the change that hidden files are no longer uploaded unless
hidden-files: true
is set. Even explicitly named files are not uploaded. This is confusing, and encourages people to turn off the safety feature completely.If I name a hidden file, it should be uploaded regardless of the setting.
To make an analogy:
ls
ignores hidden files.ls -a
shows them all.ls .gitignore
shows me the hidden .gitignore file even without the -a flag.Previous comments:
What did you expect to happen?
Explicitly named hidden files should be uploaded.
How can we reproduce it?
Many examples are in the other issues.
Anything else we need to know?
No response
What version of the action are you using?
v4.4.0
What are your runner environments?
linux, window, macos
Are you on GitHub Enterprise Server? If so, what version?
No response
The text was updated successfully, but these errors were encountered: