pwolanin
pwolanin
Yes, was discussing this with Lauri et al. I was going to work on a bigger code refactor, but let's just implement this to start.
For everything except the start can't we use tag names? e.g. ``` git log origin/8.2.x 8.0.0.. ```
Dates are fine too if you think that's more reliable. Starting on a branch for this. I'd think we want start -> 8.0.0, 8.0.0 (or whenever independent commits started going)...
How do we account for e.g. 8.3.x is branched and bug fixes to 8.2.x go there also? In general, the problem of bug fixes going 2 places.
I have started some refactoring for this on branch muti-tabs if someone wants to help work on it ping me in IRC
Is there an existing issue to move the hashing also to sha-2 instead of md5 or sha1? I'm a bit surprised that composer as a newish tool is using an...
Would love this feature also
@amitaibu I have to make a PR and not just a patch?
@amitaibu looking at the OG code, I'm curious about the use of the og.settings - this is the only place you store the entity type + bundle of all groups?
Here's a start on one added method + a couple test methods https://gist.github.com/pwolanin/2defb04b72d07328fcd0af39be4b99f2