Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Checking out wrong commit?
See original GitHub issueI just introduced a failing test into the main branch of a project; the failing tests (introduced in the commit triggering the build) appeared not to have run in the PR build.
When I look at the actions/checkout output, I am surprised by what I see.
Specifically, the build is running on commit 2dca06e – however, actions/checkout appears to be merging the prior commit – c0121d5 – (without the tests) into the project’s main branch.
Is this expected?
The project’s checkout configuration is completely vanilla: https://github.com/golangci/golangci-lint/blob/master/.github/workflows/pr.yml#L46
Issue Analytics
- State:
- Created 3 years ago
- Reactions:44
- Comments:24 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This looks quite serious (allows to sneak not validated code as valid)
@ericsciple is there any specific timeline for this?
I believe this is a dupe of #237, please see my comment here: https://github.com/actions/checkout/issues/237#issuecomment-667158637