Gonna have to try that out. I think it would have told interesting stories on some past repos.
I wish ''co-authored by AI' was easy to flag in vcs.
Gonna have to try that out. I think it would have told interesting stories on some past repos.
I wish ''co-authored by AI' was easy to flag in vcs.
This would have no effect in my team where everyone does whatever they want in git lol
They're bash/shell- and bin-dependent commands rather than Git commands. I use Nushell.
Transformed to Nushell commands:
git log --format=format: --name-only --since="1 year ago" | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20git shortlog -sn --no-mergesgit shortlog -sn --no-merges --since="6 months ago"git log -i -E --grep="fix|bug|broken" --name-only --format='' | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20git log --format='%ad' --date=format:'%Y-%m' | lines | str trim | where (is-not-empty) | uniq --countgit log --oneline --since="1 year ago" | find --ignore-case --regex 'revert|hotfix|emergency|rollback'/edit: Looks like the lines have whitespace or sth. Replaced lines --skip-empty with lines | str trim | where (is-not-empty).
command aliases
def "gits most-changed-files" [] { git log --format=format: --name-only --since="1 year ago" | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20 }
def "gits who" [] { git shortlog -sn --no-merges }
def "gits who6m" [] { git shortlog -sn --no-merges --since="6 months ago" }
def "gits fixes" [] { git log -i -E --grep="fix|bug|broken" --name-only --format='' | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20 }
def "gits aliveness" [] { git log --format='%ad' --date=format:'%Y-%m' | lines | str trim | where (is-not-empty) | uniq --count }
def "gits firefighting" [] { git log --oneline --since="1 year ago" | find --ignore-case --regex 'revert|hotfix|emergency|rollback' }
People like this author stress me out. But that’s a me thing. Nothing against them.
I get what you're saying. To me, this reads like someone who takes pride in forming assumptions (and biases) about a team before speaking to any of its members. A fun game for them, perhaps, but less fun for the folks they are trying to pigeonhole.
I guess there's a fine line between collecting information to have a productive, data-driven conversation, and doing it to avoid having a conversation entirely.
Also seems like they're more interested in connecting with the boss than the developers themselves, which is probably something you need to do as a contractor, but yeah, it does alienate other developers.
Not sure why, seems just like useful advice. It sounds like the author does contracting of some sort, so having tools to quickly orient around a new codebase makes a lot of sense.
Why on earth would this stress you out?
ha, its all how is the team performing and who can be fired or something. when I look at a repo its more what is this thing.
I just use "Claude 'explain this code like I'm an idiot use git to do it. Make no mistakes'"
all 6 comments