Skip to content

Conversation

surt91
Copy link
Collaborator

@surt91 surt91 commented Jun 18, 2025

No description provided.

@surt91 surt91 force-pushed the ci/add-gitleask branch from 3004fb7 to e5413b3 Compare June 18, 2025 06:33
@surt91 surt91 force-pushed the ci/add-gitleask branch 2 times, most recently from bfd5959 to 21426f1 Compare June 18, 2025 06:38
@surt91 surt91 force-pushed the ci/add-gitleask branch from 21426f1 to fb7ac88 Compare June 18, 2025 06:41
@surt91 surt91 requested a review from marcusleg June 18, 2025 06:43
@marcusleg
Copy link
Member

marcusleg commented Jun 18, 2025

Looks good. However our quality-gate job did not run as it seems.

@surt91
Copy link
Collaborator Author

surt91 commented Jun 18, 2025

Looks good. However our quality-gate job did not run as it seems.

Well, it did not run, because our quality-gate workflow is not yet merged (but the rule to wait for it is already in effect).
We need to merge #13 before we can merge anything else.

Copy link
Member

@marcusleg marcusleg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha! Feed free to merge this PR when it's ready..

@surt91 surt91 enabled auto-merge (squash) June 18, 2025 08:21
@surt91 surt91 merged commit a513991 into main Jun 18, 2025
20 checks passed
@surt91 surt91 deleted the ci/add-gitleask branch June 18, 2025 09:08
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