Closed samreid closed 1 year ago
I have a working prototype, but I'm questioning the value of this tool for trunk-based development. Between gravity and orbits 1.6 rc1 and rc4 there were 1490 commits that referenced 208 different issues. Here is that output:
Between gravity and orbits 1.6 rc1 and rc4 there were 1490 commits that referenced 208 different issues
Due to the uncertain helpfulness of this issue, let's close it for now. Next time we want to compare 2 branches we can give it another try if we want. Also caution the script doesn't re-checkout master at the end.
For the PhET-iO Project Board, we discussed that it would be nice to be able to see all the commits between 2 versions. This can help us know what we may need to maintenance release, or what QA should test. This is like a "bottom up" dense approach to change logs, which is described in https://github.com/phetsims/tasks/issues/1084
Following https://stackoverflow.com/questions/18679870/list-commits-between-2-commit-hashes-in-git, I checked dependencies.json for gravity and orbits 1.6.0-rc.1 and 1.6.0-rc.4 to see changes in the studio repo
How would this work if there is branch divergence (no ancestry path from one SHA to the other?)
Anyways, if we had a process that compared package.jsons (possibly from 2 different points in the same repo), it could help us aggregate reports like this.
Tagging @zepumph @arouinfar and @kathy-phet and @jonathanolson since we discussed it together.
Also, I have a little deja vu, did we do this before?