Unexpected failure in GitHub Action run
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
Direzione di ricerca
Inizia da .github/workflows/book.yml su main e dalla versione nella pull request #579, quindi esamina l’esecuzione del workflow 6003953262 e il passaggio actions/checkout che usa github.head_ref. Confronta il contesto dell’evento, il repository estratto e i refs disponibili per spiegare il fallimento. Il lavoro è completo quando sono documentati la versione del workflow e il ref utilizzati e viene identificata la configurazione necessaria affinché il workflow del PR venga eseguito correttamente.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
In a recent pull request (https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/579), one of our GitHub Action (GHA) workflow runs failed.
Overview of failed GHAs:
Now when looking at the details of that workflow run, I noticed something interesting:
- when you click on "workflow file", it takes you to the
book.ymlfile from this branch/PR (which comes from a fork) - however the file that really got executed is actually the one on the
mainbranch of the upstream. I am so sure about this as the main branch contains the config for a matrix build for this GHA, while the branch from the PR does not have that matrix build yet)
So at the very least I am starting to wonder how GHAs really work. Seems like I might have some misunderstandings here.
My questions are:
- which GHAs are executed? the ones on the
mainbranch, or the ones on the PR branch, or both? mainand PR contain different versions of the same GHA. what happens in that case?
And lastly:
Why does this GHA run fail at all?
It seems like it is looking for a git ref hive-mind-pattern-1 and cannot find it? Possibly because that ref only exists on the fork but not on the upstream?
Do we have to configure the actions/checkout differently, so that it can find that git ref?
Right now we use ref: ${{ github.head_ref }}, which is defined as:
The head_ref or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either pull_request or pull_request_target.
I am suspecting that we are checking out the upstream repo InnerSourceCommons/InnerSourcePatterns but then trying to point to a ref that does not exist on that upsream.
Just not sure how one would configure this correctly?
- Lingua principale
- HTML
- Stelle
- 853
- Fork
- 206
- Merge medio
- 1g 23h
- PR unite (30g)
- 2
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di InnerSourceCommons/InnerSourcePatterns
-
community metrics
InnerSourceCommons/InnerSourcePatterns#935 · 1 assegnatario ·
-
community metrics
InnerSourceCommons/InnerSourcePatterns#934 · 1 assegnatario ·
-
community metrics
InnerSourceCommons/InnerSourcePatterns#922 · 1 assegnatario ·
-
community metrics
InnerSourceCommons/InnerSourcePatterns#921 · 1 assegnatario ·
-
community metrics
InnerSourceCommons/InnerSourcePatterns#915 · 1 assegnatario ·
Tutte le issue di InnerSourceCommons/InnerSourcePatterns
Issue simili
-
intake mcp-intake needs-ac needs-human-review priority:medium type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
Ikalus1988/MisakaNet#2019 · 2 commenti ·
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
-
bug github_actions
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
-
Documentation issues Aperta
Difficoltà 2/5 1-2 giorni Idoneità per principianti 72/100
-
feature
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
betagouv/acces-cible#722 ·