Skip to content
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

ci: fix 6356 follow-up #6358

Merged
merged 1 commit into from
Oct 24, 2024
Merged

ci: fix 6356 follow-up #6358

merged 1 commit into from
Oct 24, 2024

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Oct 24, 2024

Issue being fixed or feature implemented

🙈

What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

@UdjinM6 UdjinM6 added this to the 22 milestone Oct 24, 2024
Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

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

Happens :) utACK 7064eb9

@PastaPastaPasta PastaPastaPasta changed the title fix: 6356 follow-up ci: fix 6356 follow-up Oct 24, 2024
@UdjinM6 UdjinM6 merged commit 1a5bbd8 into dashpay:develop Oct 24, 2024
7 of 14 checks passed
Copy link

This pull request has conflicts, please rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants