- Issue created by @danielspeicher
- Assigned to danielspeicher
- @danielspeicher opened merge request.
- Status changed to Needs review
over 1 year ago 10:38am 6 April 2023 - 🇩🇪Germany danielspeicher Steisslingen
This is now implemented. The settings are in the menu code>admin/config/user-interface, which can be discussed and changed.
- First commit to issue fork.
- Issue was unassigned.
- Status changed to RTBC
about 1 year ago 12:51pm 8 November 2023 - 🇩🇪Germany jurgenhaas Gottmadingen
I've rebased the MR and tested it again, it's looking great and works as described.
- 🇩🇪Germany jurgenhaas Gottmadingen
This should go into the 2.x branch now. @danielspeicher I've tried to rebase but I can't change the MR to target 2.x, it's still targetting 1.x - can you please check if you can change that as the creator of the MR?
- 🇩🇪Germany danielspeicher Steisslingen
@jurgenhaas: Ok, can you please tell me what I have to do that the MR targets the new version?
- 🇩🇪Germany jurgenhaas Gottmadingen
Well, if I knew what was necessary, I could tell. When I open the MR from the link above, it opens on GitLab and show that it is configured to merge into 1.x
There should be some edit form, where the target branch can be changed. But I guess, that's only available for the creator of the MR, so I don't see it.
- 🇩🇪Germany danielspeicher Steisslingen
I can't see it either on the MR edit form. I started a rebase, but it failed. Do we have other possibilities?
- 🇩🇪Germany jurgenhaas Gottmadingen
Maybe creating a new issue fork and from there a new MR then?
