Super confused by the glob
See original GitHub issueHello 👋
Thanks for this GitHub Actions!
I’m testing it today but I got super confused by the glob:
It’s a private repository so I can’t really show more than that. But you see that I use archive/*.zip
and the glob failed to found it. But on the other hand I did ls -l archive/*.zip
just before and it worked. This seems very strange.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:10
Top Results From Across the Web
Python: confused about global and local variables
Noob question. I'm writing a program with recursive function calls - it's a game so I'm using recursion to allow the computer to...
Read more >I'm super confused about this and really need help!
I have an object oController with: -> Create Event: /// @description player stats global.level = 1; global.exp = 0; ...
Read more >Successful Decision-making in a Confused and Troubled World by
Get Beating the Global Odds: Successful Decision-making in a Confused and Troubled World now with the O'Reilly learning platform.
Read more >Confused Confusion GIF by Škoda Global - Find & Share on ...
Discover & share this Škoda Global GIF with everyone you know. GIPHY is how you search, share, ... Confused Youtube GIF by vidIQ...
Read more >Tiffany Tseng
well I guess this confirms it - finally got an email saying I'm no longer eligible for Global Entry because I live in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve solved the issue. After reading the documentation from download-artifact:
So really, the glob we are looking for is
path-to-dowloads/*/*
Thanks for your example @cecton . Here’s what I have for the release job that runs after my build:
The
ls
step confirms that the files are present but the release step doesn’t find the files. I was on v0.1.5 and upgraded to v1 as well with same result.