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

Fix case when new release commit pushed but still master used for sync #8112

Merged
merged 2 commits into from
Jan 27, 2025

Conversation

kamilchodola
Copy link
Contributor

Noticed that we have an issue that when action is triggered via new docker image publish for release branch we still keep using master image for sync tests.

Types of changes

What types of changes does your code introduce?

  • Bugfix (a non-breaking change that fixes an issue)
  • New feature (a non-breaking change that adds functionality)
  • Breaking change (a change that causes existing functionality not to work as expected)
  • Optimization
  • Refactoring
  • Documentation update
  • Build-related changes
  • Other: Description

Testing

Requires testing

  • Yes
  • No

If yes, did you write tests?

  • Yes
  • No

@kamilchodola kamilchodola requested review from rubo and a team as code owners January 27, 2025 13:24
@kamilchodola kamilchodola merged commit 1285408 into master Jan 27, 2025
79 checks passed
@kamilchodola kamilchodola deleted the kch/fix_sync_supproted branch January 27, 2025 14:18
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