Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 1 of 2

Github Actions: Inconsistent repo checkouts across jobs

We've encountered an issue where jobs within a single Github Actions workflow get different checkouts of the repo, note the different merge commit SHAs between these 2 jobs in a single workflow run:

https://github.com/linkerd/linkerd2/pull/3339/checks?check_run_id=207228659#step:2:972

https://github.com/linkerd/linkerd2/pull/3339/checks?check_run_id=207243373#step:2:979

 

I believe this order of events is the root cause:

1. job1 runs actions/checkout

2. master branch changes

3. job2 runs actions/checkout

 

Is this expected behavior? Is there any way to guarantee all jobs within a single run of a workflow get the same copy of the repo?

 

A secondary priority is a clear way to choose whether we want to test merge commits on PRs, but testing consistent code across all jobs is far more important.

 

Filed a related issue in the actions/checkout repo, as it wasn't originally clear to me whether this was an issue in Github Actions in general or specifically in checkout/actions:

https://github.com/actions/checkout/issues/27

 

 

1 Reply
Community Manager
Message 2 of 2

Re: Github Actions: Inconsistent repo checkouts across jobs

 @siggy,

 

Thank you for being here and apologies for the delay in response. Thanks for opening the issue on the actions repo, at this time I don't have any updates but wanted you to know the team is checking those issues and will reply as soon they can. Thanks again!


Best,
AndreaG

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!