-
Notifications
You must be signed in to change notification settings - Fork 4
Disable shallow clone in maven_push.yml for Sonar analysis #398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: thomasturrell <1552612+thomasturrell@users.noreply.github.com>
|
@copilot please rebase with main and resolve conflicts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR disables shallow cloning in the maven_push.yml workflow to enable proper Sonar analysis by providing full git history access.
- Added
fetch-depth: 0to the checkout step in the maven_push workflow
Co-authored-by: thomasturrell <1552612+thomasturrell@users.noreply.github.com>
|



Description
Sonar requires full git history for proper analysis. Shallow clones cause warnings and incomplete scans.
Added
fetch-depth: 0to the checkout step in.github/workflows/maven_push.yml. Merged with main branch to incorporate the latest workflow updates including checkout action upgrade to v5 and cache-dependency-path configuration.Final configuration:
The merge with main also brought in improvements to Maven caching configuration.
Resolves #397
Checklist:
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.