(DMs are open.)
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Getting a docker-based action going was tough as there are a lot of little details that are easy to miss, e.g. inputs **need** to be passed in via args, images from Docker **must** use args from a step and not actions.yml
-
Thanks for the feedback... I agree that using docker-based actions is more challenging. I'll take a look at how we can improve this.
- Još 5 drugih odgovora
Novi razgovor -
-
-
I couldn't find docs explaining how to test my action before releasing it. Later realized I could point the action to head.
-
Great feedback. We definitely need to document this, but I think we need a better way to test an action than that. What does your action do? Can you point me to it?

- Još 4 druga odgovora
Novi razgovor -
-
-
A lot of the examples I found were done in an old way, with outdated screenshots. It took a long time to get mine working.
-
Sorry to hear that it took a long time. When you say the "old way" - you mean the old HCL syntax? Were you finding examples in our docs or other places around the internet? Can I ask what you were building (could you share your workflow with me)?
- Još 2 druga odgovora
Novi razgovor -
-
-
The docs are fine, but not being able to reproduce the same environment in self-host is a bummer (debugging issues that only appear on the runner can be pretty hard). Ended up using Docker to do a similar job (https://github.com/Gabrielcarvfer/GitHubRunnersWithDocker …).
-
Thanks for the feedback... out of curiosity, did you try running the packer scripts? I don't know how easy it is to take the packer scripts that target a VHD and make them emit a Docker image.https://github.com/actions/virtual-environments …
- Još 2 druga odgovora
Novi razgovor -
-
-
Global scope secrets
-
Can you tell me more about this? You want secrets that live in the user/organization instead of the repository?
- Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.