+ [2019-09-16T18:37:18Z] briian jhass: the response not being 404 from the /refs/tags response was enough for me, the data wasnt really important
+ [2019-09-16T18:37:30Z] briian so any endpoint that served a similar purpose would have been perfect
+ [2019-09-16T18:57:48Z] BtbN Hm, is there really no way to manually re-run a Workflow/Action?
+ [2019-09-16T19:04:01Z] BtbN Without manually being able to re-run a Workflow this is close to useless sadly. Happens way too frequently that there is a temporary outage on some service the workflow connects to to download things from.

message no. 174552

Posted by BtbN in #github at 2019-09-16T09:33:04Z

Is someone aware of a TravisCI to GH Actions migration guide? It seems like I could just write down our current travis.yml as github workflow, but I'm sure there's more efficient things to do there.
+ [2019-09-17T13:15:08Z] tshirtman so every time i want to add actions to a project, i apparently need to first create a workflow the old way, and i need to merge that, and then when i edit this workflow again, i get the button to upgrade to the new system, and i need to remove the workflow i just created and i knew i didn't need to create, then i can add the new files because it's now looking for them. Is there a clean way to
+ [2019-09-17T13:15:14Z] tshirtman create directly the new way instead of polluting my history ?
+ [2019-09-17T13:15:55Z] tshirtman i think it's the 3rd project where i add actions and everytime i wonder what i'm missing because i don't have a way to directly enable the new way
+ [2019-09-17T17:19:55Z] Naros I'm setting up some GitHub Actions and I have a question about token access.
+ [2019-09-17T17:20:34Z] Naros I have repo A where I have an action where I send a POST to repo B's endpoint https://api.github.com/repos/<owner>/<repo>/dispatches