- Issue created by @darren.fisher
- 🇬🇧United Kingdom darren.fisher
See !MR9 for the fix. Unassigning myself. Please take a look when you get a chance!!
- 🇬🇧United Kingdom darren.fisher
I've made a bit of a mess of this branch because it seemed to be forked from the 1.x branch and not the 2.x. Fixing now.
- 🇬🇧United Kingdom darren.fisher
That's what I thought. When I branched in the issue it said 1.x was the default branch. I'll close the 1.x MR. If you could look at MR!10 and let me know what you think? I also added tests which are throwing a warning because the install hook in the module should be in an install file but we should probably deal with that in a separate issue. Do you agree or should I fix that here as well?
- 🇬🇧United Kingdom darren.fisher
It looks like 1.x is still the default branch in gitlab hence all the confusion around multiple branches and merge requests. Are you able to set the default branch to 2.0.x or 2.x? Not sure which one you want to use? See attached screenshot.
- 🇵🇱Poland lamp5 Rzeszow
It looks like settnings on Gitlab does not populate settings from Drupal project page. Done.
-
lamp5 →
committed d0d5fde2 on 2.0.x authored by
darren.fisher →
Resolve #3509709 "Config schema 2"
-
lamp5 →
committed d0d5fde2 on 2.0.x authored by
darren.fisher →
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇬🇧United Kingdom darren.fisher
What's the release cycle for this module? It would be nice to have this as a tagged release so I can make sure my recipes run without relying on the dev branch!
- 🇵🇱Poland lamp5 Rzeszow
Excuse me? It is opensource. I spend my free time to maintain this so release cycle is based my humor.
- 🇬🇧United Kingdom darren.fisher
Sorry I think you might have misunderstood me or perhaps I worded this badly!! I was just asking if you have a release planned at all? Didn't mean any offence!!