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: #5242 - Replace phosphate at the end with petide causes cycled polymer #5259

Merged
merged 2 commits into from
Aug 9, 2024

Conversation

rrodionov91
Copy link
Collaborator

@rrodionov91 rrodionov91 commented Aug 8, 2024

How the feature works? / How did you fix the issue?

  • changed usage of previous/next node to previous/next node in same chain for replacing sequence items through the library

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

- changed usage of previous/next node to previous/next node in same chain for replacing sequence items through the library
@rrodionov91 rrodionov91 changed the title #5242 - Replace phosphate at the end with petide causes cycled polymer Backmerge: #5242 - Replace phosphate at the end with petide causes cycled polymer Aug 9, 2024
@rrodionov91 rrodionov91 merged commit 5506be9 into master Aug 9, 2024
5 checks passed
@rrodionov91 rrodionov91 deleted the 5242-replace-phosphate-issue branch August 9, 2024 12:29
Guch1g0v pushed a commit that referenced this pull request Oct 17, 2024
…cled polymer (#5259)

- changed usage of previous/next node to previous/next node in same chain for replacing sequence items through the library
- fixed replacement of single selection of two chains
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment