-
-
Notifications
You must be signed in to change notification settings - Fork 827
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
dev/core#4127 move standalone profile modification to userSystem #25574
Conversation
No issue was found matching the number given in the pull request title. Please check the issue number. |
(Standard links)
|
Fixed the style. It will need a squash during merging. |
@herbdool we actually disabled the ability to squash during merging - it isn't great froma commit history point of view |
@eileenmcnaughton okay, I'll do a force push. I'm used to the Backdrop workflow on github, where we always squash PRs when merging. I haven't noticed any difference between the two since it just shows up as one commit per PR in the main branch. |
@herbdool yeah - if you squash you get one commit, otherwise you get 2 with the difference between the merge commit & the non-merge commit clear & no 'leakage' of committer from merger |
It's ready again. |
test this please Jenkins |
Fixes https://lab.civicrm.org/dev/core/-/issues/4127