Skip to content

Fixes #298: Use deactivate_branch to handle new change diffs correctly #306

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Aug 8, 2025
Merged

Fixes #298: Use deactivate_branch to handle new change diffs correctly #306

merged 1 commit into from
Aug 8, 2025

Conversation

@tom0010
Copy link
Contributor

@tom0010 tom0010 commented Jul 30, 2025

Fixes: #298

  • Use deactivate_branch to handle new change diffs correctly

@CLAassistant
Copy link

CLAassistant commented Jul 30, 2025 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

@jnovinger jnovinger requested a review from a team July 30, 2025 15:04
@jnovinger jnovinger changed the title Fix #298 Fixes #298: Use deactivate_branch to handle new change diffs correctly Jul 30, 2025
@jnovinger jnovinger merged commit b4b4fa2 into netboxlabs:main Aug 8, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jnovinger jnovinger jnovinger approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Replacing M2M values in a branch causes conflicts

3 participants

@tom0010 @CLAassistant @jnovinger