+ [2020-04-29T18:49:29Z] kreyren I HUGGING CALLED IT
+ [2020-04-29T18:51:06Z] kreyren What now >.<
+ [2020-04-29T18:56:09Z] kreyren is just going to press retry every 12 hours until it works
+ [2020-04-29T19:16:07Z] jhass not much to do except writing support about it
+ [2020-04-29T23:36:38Z] pat64 Does GITHUB_TOKEN not work with hub when the workflow runs in a container?

message no. 179893

Posted by Viking667 in #github at 2020-04-29T00:03:03Z

I'm noticing a strange problem. I forked a project, they've updated from 7.1.10-xx-gxyzabcdef to 7.2.0-xx-gxyzabcdef, yet even though I've done "git pull upstream master" my tags didn't change to match upstream.
+ [2020-04-30T00:08:29Z] drleviathan the workflow has the GITHUB_TOKEN available
+ [2020-04-30T00:09:18Z] drleviathan I'm pretty sure it is also available in the container.
+ [2020-04-30T00:11:49Z] drleviathan at one time I was examining the env of the container. I didn't take notes of all the environment variables passed, but you carefully look at the command that runs a docker container you can see the names of the variables passed.
+ [2020-04-30T00:12:27Z] drleviathan and if isn't there you could pass it manually
+ [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.