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

Backmerge: #6098 - Two sense to antisense connection order problem #6408

Conversation

aproskurnov
Copy link
Collaborator

Check list

  • unit-tests written
  • e2e-tests written
  • documentation updated
  • PR name follows the pattern #1234 – issue name
  • branch name doesn't contain '#'
  • PR is linked with the issue
  • base branch (master or release/xx) is correct
  • task status changed to "Code review"
  • reviewers are notified about the pull request

@rrodionov91 rrodionov91 force-pushed the 6098-backmerge-two-sense-to-antisense-connection-order-problem branch from 1aed4eb to 747d572 Compare February 10, 2025 15:29
@rrodionov91 rrodionov91 merged commit 9c356a8 into master Feb 10, 2025
10 checks passed
@rrodionov91 rrodionov91 deleted the 6098-backmerge-two-sense-to-antisense-connection-order-problem branch February 10, 2025 16:44
rrodionov91 pushed a commit that referenced this pull request Feb 10, 2025
@rrodionov91 rrodionov91 changed the title Backmerge: #6098 Two sense to antisense connection order problem (#6401) Backmerge: #6098 Two sense to antisense connection order problem Feb 10, 2025
@rrodionov91 rrodionov91 changed the title Backmerge: #6098 Two sense to antisense connection order problem Backmerge: #6098 - Two sense to antisense connection order problem Feb 10, 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.

Adding second chain with antisese chain to the canvas cause layout problem
4 participants