-
I tested the pr-mode switch and activated it for the first time. It seems to me that checking out only the last commit is not sufficient for that in a GitHub action. I'm suspecting that I'll need to check out all commits of the PR, and probably also one more commit. Can you confirm what's necessary for this? I had a look at the docs, and didn't find any docs about the I'm using Once it is known what is necessary, a minimal example for GitHub actions would be nice. For now I went with the following for PRs, some changes might be necessary when running on the main branch.
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
UPDATE: When running with a fetch depth of 1, I saw an error message like this. Actually it was not fatal: the analysis continued, but found no changes, therefore no violations. If it could not process an option, I'd assume it would be better for the process to fail instead of reporting everything is find.
|
Beta Was this translation helpful? Give feedback.
-
@ahus1 everything works as expected, you do not need to do any additional git-related operations as the action will do it all for you. All needed for this is the initial checkout with the full history, the one we are telling in the docs about. I could also look at the build you are trying to set up and check if everything is OK! |
Beta Was this translation helpful? Give feedback.
@ahus1 everything works as expected, you do not need to do any additional git-related operations as the action will do it all for you. All needed for this is the initial checkout with the full history, the one we are telling in the docs about.
I could also look at the build you are trying to set up and check if everything is OK!