GitHub Community
GitHub workflows started to fails #27056
-
|
Workflows pinned actions with SHA have been failing since yesterday.
Workflow Job: Fixes toggle method in files field dropdownIt works when I pin it with version instead of SHA of v2: Works: |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments
-
|
That commit doesn’t seem to exist in the |
Beta Was this translation helpful? Give feedback.
-
|
airtower-luna:
Do you mean |
Beta Was this translation helpful? Give feedback.
-
|
Yes, exactly. I have no idea why, but trying to view the commit doesn’t work (404). |
Beta Was this translation helpful? Give feedback.
-
|
This is SHA of |
Beta Was this translation helpful? Give feedback.
-
|
Also, it was already working like this. It suddenly stopped working yesterday. |
Beta Was this translation helpful? Give feedback.
-
|
The issue may not be exactly about pinning the SHA either. The only error I can see is this. |
Beta Was this translation helpful? Give feedback.
-
|
As I understand the documentation ( |
Beta Was this translation helpful? Give feedback.
-
|
As you said, using the latest version commit hashes fixed the issue. But since it broke while working with tag hashes, I reported the situation to the github support team. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
👋 Hey @afbora, This was broken by an internal change we made, sorry about that. I’ve disabled that change, so referencing a tag by the SHA object ID should work for now. As referenced in our documentation, the intended use is using a commit SHA rather than other objects. |
Beta Was this translation helpful? Give feedback.
-
|
You use too many acronyms which I have no idea of their meaning such as Pull and here the use of SHA. |
Beta Was this translation helpful? Give feedback.
-
|
To learn Git terms, take a look at the Git Book. 🙂 |
Beta Was this translation helpful? Give feedback.
👋 Hey @afbora,
This was broken by an internal change we made, sorry about that. I’ve disabled that change, so referencing a tag by the SHA object ID should work for now.
As referenced in our documentation, the intended use is using a commit SHA rather than other objects.