Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
Currently, in order to execute a script in the same repository and the exact commit that is running, the repository needs to be explicitly checked out first, or the script needs to be retrieved otherhow (say using
curl | bash).Since self-repository syntax was introduced for 'uses' steps, it would be really handy to have it available for 'run' steps as well.
Internatlly, when a multiline run block is provided, the runner does already save it to a temporary file and pass that to the shell.
Therefore, this would only require to checkout the repo (as with same-repository actions/workflows) instead.
All reactions