Replies: 3 comments 1 reply
-
If you're continuously getting fails on commit/push, check out the documentation. It might be a bit annoying to sift through, but Github usually has some helpful hints as to what's throwing the error and how to best remedy it. This video helped me out when I was exploring workflows, maybe watch it through and see if you can spot where your workflow is hitting a block. If you've checked your syntax with the documentation and everything matches but you still get errors, post a bit more information with any sensitive data censored for security. Be sure to update and mark as 'answered' if the video or docs end up solving the issue, thanks. |
Beta Was this translation helpful? Give feedback.
-
Thanks!
The issue I am raising is more about the development journey I am taking, rather than about a failure of job. I mean: when developing, jobs will inevitably fail - just like with any other coding endevour. The stark difference with github actions is that I need to commit to a remote repo to test it. Plus, how do I debug and do post-mortem analysis on the filesystem hosting the action? Say I fail to notice a missing comma (which fails a script step), or I just want to add a temporary debug print - do I actually need to cement a commit in the repo's history for that?
Like I said above: I must be doing sth wrong? My experience with writing actions so-far is that it is painfully slow and ineffective.
On 11 Nov. 2022 1:03 am, Graham Zemel ***@***.***> wrote:
If you're continuously getting fails on commit/push, check out the documentation<https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions>. It might be a bit annoying to sift through, but Github usually has some helpful hints as to what's throwing the error and how to best remedy it.
This video<https://www.youtube.com/watch?v=rDcswW9NOnc> helped me out when I was exploring workflows, maybe watch it through and see if you can spot where your workflow is hitting a block.
If you've checked your syntax with the documentation and everything matches but you still get errors, post a bit more information with any sensitive data censored for security. Be sure to update and mark as 'answered' if the video or docs end up solving the issue, thanks.
—
Reply to this email directly, view it on GitHub<#38821 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZN33QWKTYFNPOLMFXCAOGLWHV5FXANCNFSM6AAAAAAR5BR5LQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering.
https://www.mailguard.com.au/mg
Report this message as spam<https://console.mailguard.com.au/ras/24b2Qaok0t/4AVSYfvTrblQ7Nebji401P/3>
|
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi.
Sanity check: say I want to introduce a new workflow, triggered by a PR. Here's what I do:
Surely there's a better way? Tried 'nektos/act', but it really falls short, failing on stuff that actually works on github.
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions