latest 20 messages by pat64

+ [2020-05-09T07:40:08Z] pat64 Can I remove old GitHub Actions caches?
+ [2020-05-08T15:19:32Z] pat64 Can I remove old GitHub Actions caches?
+ [2020-05-03T20:55:51Z] pat64 Does the GitHub Actions UI provide information about saved workflow caches?
+ [2020-05-03T10:28:04Z] pat64 I can't view currently saved GitHub Actions caches, can I?
+ [2020-05-01T14:59:11Z] pat64 Yes, good idea, I'll try that, too.
+ [2020-05-01T14:55:53Z] pat64 jhass: I think so, but I'm not 100% sure and don't want to say something wrong. I think I'll have to build a minimal example...
+ [2020-05-01T14:53:28Z] pat64 jhass: Yes, I did set it with env: GITHUB_TOKEN: {{ secrets.GITHUB_TOKEN }}. Furthermore, the hub docs say, it only needs a good GITHUB_TOKEN env var to work. And if I echo the variable inside the container, it shows "***" which I think means that it should be a good token because it gets cencored for the log output.
+ [2020-05-01T14:40:35Z] pat64 jhass: Thank you for the clarification. I don't get it, then. As soon as I add `container: ubuntu:latest` (so it isn't even another distribution or something), the hub CLI tool doesn't work anymore and shows 401 Unauthorized. :/
+ [2020-05-01T14:31:41Z] pat64 jhass: Yesterday, did you mean to say that it's possible that GITHUB_TOKEN is restricted to non-container jobs and won't work in a container, even though the commands are the same?
+ [2020-04-30T08:36:41Z] pat64 If I use a simple `hub release create` command to create a dummy release it works - and stops working as soon as I add `container: ubuntu:latest` to run it in a container
+ [2020-04-30T08:36:02Z] pat64 jhass: I've already been reading that page (yesterday and again just now) and couldn't find anything that helps with my issue. Can you explain a little bit more what you meant?
+ [2020-04-30T06:27:17Z] pat64 Sooo, if GITHUB_TOKEN is there - why doesn't the hub CLI tool work? I get "Error fetching releases: Unauthorized (HTTP 401)" even though all I should have to do for authorization is to set a valid GITHUB_TOKEN
+ [2020-04-30T06:26:05Z] pat64 drleviathan: You're right. I did echo GITHUB_TOKEN and it showed *** only. Meaning there is something there which is automatically being cencored for the log.
+ [2020-04-29T23:36:38Z] pat64 Does GITHUB_TOKEN not work with hub when the workflow runs in a container?
+ [2020-04-26T12:54:12Z] pat64 Will GitHub Actions artifacts always be ZIP files? Or can I have another binary file directly available as an artifact, too?
+ [2020-04-26T06:57:39Z] pat64 Will GitHub Actions artifacts always be ZIP files? Or can I have another binary file directly available as an artifact, too?
+ [2020-04-25T14:13:31Z] pat64 Will GitHub Actions artifacts always be ZIP files? Or can I have another binary file directly available as an artifact, too?
+ [2020-04-22T16:36:18Z] pat64 jhass: Using wget -qO - https://api.github.com/repos/jgm/pandoc/releases/latest | grep -o '"[^"]*/download/[^"]*-amd64.deb"' | grep -o '[^"]*' now ? Thanks for the help
+ [2020-04-22T16:22:59Z] pat64 I'll see what I can find. Thanks :)
+ [2020-04-22T16:22:27Z] pat64 (I thought, since "latest" worked in the filename for shellcheck, maybe GitHub has added support for substituting "latest" in assets, too)