Skip to content

Separate Compare DS build and compare steps#13535

Merged
jan-cerny merged 1 commit intoComplianceAsCode:masterfrom
Mab879:update_gh_actions_2
Jun 6, 2025
Merged

Separate Compare DS build and compare steps#13535
jan-cerny merged 1 commit intoComplianceAsCode:masterfrom
Mab879:update_gh_actions_2

Conversation

@Mab879
Copy link
Copy Markdown
Member

@Mab879 Mab879 commented Jun 4, 2025

Separate Compare DS build and compare steps.

@Mab879 Mab879 added this to the 0.1.78 milestone Jun 4, 2025
@qlty-cloud-legacy
Copy link
Copy Markdown

Code Climate has analyzed commit 62d23b5 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 61.9% (0.0% change).

View more on Code Climate.

@jan-cerny jan-cerny self-assigned this Jun 5, 2025
@jan-cerny
Copy link
Copy Markdown
Collaborator

@Mab879 Why does the output of Compare DS / Generate Diff (pull_request_target) look like it's executed without these changes? Do I need to do something to trigger the new version of the job?

@Mab879
Copy link
Copy Markdown
Member Author

Mab879 commented Jun 5, 2025

I have example runs on my fork, Mab879#42

The pull request target job config is pulled from the base branch, not the PR so you will not see the change fully on this.

To trigger a comment you need "change" detected by CTF.

@jan-cerny jan-cerny merged commit b7c78f0 into ComplianceAsCode:master Jun 6, 2025
133 of 134 checks passed
@Mab879 Mab879 deleted the update_gh_actions_2 branch June 9, 2025 12:49
@Mab879 Mab879 mentioned this pull request Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants