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

update to Moq 4.18.3 #974

Merged
merged 1 commit into from
Dec 16, 2022
Merged

update to Moq 4.18.3 #974

merged 1 commit into from
Dec 16, 2022

Conversation

SimonCropp
Copy link
Contributor

No description provided.

@martincostello
Copy link
Member

Are we dropping the guidance to merge to v724-or-v730 instead of the default branch?

@SimonCropp
Copy link
Contributor Author

@martincostello sorry. i completely forgot about that convention.

yes my preference would be to move to a "direct to main branch" model.

@martincostello
Copy link
Member

I’m happy with that if @joelhulen’s cool with it - it’s less effort 😆

As long as we’re all doing the same thing so we don’t end up with two different branches and a merge headache later.

@joelhulen
Copy link
Member

@SimonCropp and @martincostello, I'm cool with that change. It's less confusing and less effort this way.

@martincostello martincostello mentioned this pull request Dec 16, 2022
@martincostello martincostello merged commit 233a26d into master Dec 16, 2022
@martincostello martincostello deleted the update-to-Moq-4.18.3 branch December 16, 2022 16:56
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.

3 participants