git-loom 1.0
-2 points by skade
-2 points by skade
You can do something similar in vanilla git with git rebase --rebase-merges --update-refs --interactive. You create an integration branch based on master where you merge in all your features. Then when you want to update a feature branch you make a commit on integration and move it onto the appropriate feature branch (which gets automatically updated). The downside is that it's inconvenient to update the integration branch if you ever update the feature branches independently. But otherwise it works like the classic feature branch rebasing workflow.
I flagged this as spam, for this reason.
But I expect disagreement and would like feedback. This is not a link to a repo, but a link to a subset of a repo, served by another webserver, yet still almost completely devoid of human words by the looks of it. Should this really clear the bar the mods set for Lobsters a few days ago?
What’s the benefit of suppressing this post? It saves some people the annoyance of reading AI-generated text? At the expense of the community learning about a potentially valuable new tool, which was AFAICT designed by humans.
I think the intention of the spam rule is to save us from low-value content produced to promote a product or drive monetized clicks. Before LLMs there was plenty of that produced by “content farms” of bored human writers; now LLMs churn it out. But that doesn’t mean all writing by LLMs is “slop.” It depends on the usefulness and novelty of what they’re writing about. But judging that intakes more effort than just noticing grammatical quirks.