pull down to refresh

51 sats \ 7 replies \ @k00b 22 May \ on: Stacker Saloon

What kind of cookie do I get for interactively rebasing 6k lines? It's at least somewhat pleasurable having bots to help:

  1. plan and plan and plan which logical parts there are
  2. plan the sequence to apply them
  3. create a smoke test as criteria verifying each commit applies without breaking stuff
  4. spend 10s of dollars in tokens to execute

Also, interactive rebases are a surprisingly (to me) great way to interrogate overall structure. In hindsight it's obvious - looking at smaller units of code always you to spot more - but it's a new to me, Mr. Monolith Career-Without-Reviewers, III.

write
compose
124 sats \ 2 replies \ @WeAreAllSatoshi 23 May

interactive rebase is my jam

reply
51 sats \ 1 reply \ @k00b 23 May

I should probably read about how to get good at it.

I assume it's mostly a thing when you are committing regularly (which I do not do). I end up with one huge commit most of the time.

reply
124 sats \ 0 replies \ @WeAreAllSatoshi 23 May

I use it a lot when auto squashing fixup commits, which depends on having multiple commits to squash into.

it definitely helps point out when you muddy the waters on commits, when things should be broken up.

reply
51 sats \ 2 replies \ @k00b 23 May

New record for a single tick.

reply
145 sats \ 1 reply \ @SimpleStacker 23 May

wooo

are you connecting via api or subscription?

reply
1 sat \ 0 replies \ @k00b 23 May

This is via Cursor which, I'm told, passes along the costs of using the API once you exceed your quota. I'm yet to use a Anthropic or OpenAI harness - but I have subscriptions to both.

reply
1 sat \ 0 replies \ @k00b 22 May

There's no inverse (child of tip) of HEAD~1 (parent of tip) because there can be many children. But if you give git a descendant to move toward, it can do it.

git config --global alias.child '!f() { if test "$#" -gt 0; then target="$1"; else target="@{-1}"; fi; next="$(git rev-list --reverse --first-parent HEAD.."$target" | sed -n "1p")"; test -n "$next" && git switch --detach "$next" || { echo "no next commit toward $target"; return 1; }; }; f'
reply