Earlier quoted context omitted.
how do you trust the code claude wrote? don't you get anxiety "what if there's an error in tui code and it would mess up my git repo"?
Isn't it this case no matter who wrote the code? How do you ever run anything if you're worried about bugs?
I found a useful Git one liner buried in leaked CIA developer docs
161–170 of 273 posts
Re: I found a useful Git one liner buried in leaked CIA developer docs
#162I use `master` in all my repos because I've been using it since forever and it never has once occurred to me "oh shit I better change it to `main` this time in case `master` may offend somebody some day. Unfortunately, that's the last thing on my mind when I'm in programming mode. Now that everything is `master`, maybe it is just a simple git command to change it to `main`. But, my fear is it'll subtly break somethin…
Yeah, it's not like 99% of the world has already switched from master to main already (without any major problems) ...
Re: I found a useful Git one liner buried in leaked CIA developer docs
#163I currently have a TUI addiction. Each time I want something to be easier, I open claude-code and ask for a TUI. Now I have a git worktree manager where I can add/rebase/delete. As TUI library I use Textual which claude handles quite well, especially as it can test-run quite some Python code.
Can you explain TUI? I have never heard this before
Re: I found a useful Git one liner buried in leaked CIA developer docs
#164https://gist.github.com/andrewaylett/27c6a33bd2fc8c99eada605...
But actually nowadays I use JJ and don't worry about named branches :).
Re: I found a useful Git one liner buried in leaked CIA developer docs
#165Earlier quoted context omitted.
At Meta, when this mass push for the rename happened across the industry, a few people spent nearly the full year just shepherding the renaming of master to main, and white box/black box to allowlist/blocklist. This let them claim huge diff counts and major contributions to DEI and get promos.
Same at my org at the time, blacklist was nixed, no matter how many times the question, "What color is ink on a page?" was brought up.
Blocklist makes more sense in most scenarios.
Re: I found a useful Git one liner buried in leaked CIA developer docs
#166I use `master` in all my repos because I've been using it since forever and it never has once occurred to me "oh shit I better change it to `main` this time in case `master` may offend somebody some day. Unfortunately, that's the last thing on my mind when I'm in programming mode. Now that everything is `master`, maybe it is just a simple git command to change it to `main`. But, my fear is it'll subtly break somethin…
Re: I found a useful Git one liner buried in leaked CIA developer docs
#167So effectively "I just discovered xargs"? Not to disparage OP but there isn't anything particularly novel here.
This feels like gatekeeping someone sharing something cool they've recently learned. I personally lean more towards the "let's share cool little productivity tips and tricks with one another" instead of the "in order to share this you have to meet [entirely arbitrary line of novelty/cleverness/originality]." But each to their own I suppose. I wonder how you learned about using xargs? Maybe a blog-post or article not…
Re: I found a useful Git one liner buried in leaked CIA developer docs
#168So effectively "I just discovered xargs"? Not to disparage OP but there isn't anything particularly novel here.
Re: I found a useful Git one liner buried in leaked CIA developer docs
#169I use `master` in all my repos because I've been using it since forever and it never has once occurred to me "oh shit I better change it to `main` this time in case `master` may offend somebody some day. Unfortunately, that's the last thing on my mind when I'm in programming mode. Now that everything is `master`, maybe it is just a simple git command to change it to `main`. But, my fear is it'll subtly break somethin…
[flagged]
Re: I found a useful Git one liner buried in leaked CIA developer docs
#170 git branch --format '%(if:equals=gone)%(upstream:track,nobracket)%(then)%(refname:short)%(end)' --omit-empty | xargs --verbose -r git branch -D
It deletes all the branches for which remotes were deleted. GitHub deletes branches after PR was merged. I alias it to delete-merged