Maybe using git notes for the conversation or conversation summary is better.
Claude Session URL appended to commit messages and PR descriptions by default
181–190 of 257 posts
Re: Claude Session URL appended to commit messages and PR descriptions by default
#182I consider my prompts and prompting style to be trade secrets. I've developed a very efficient and productive workflow for myself over the years without tutorials, without books, etc. Anthropic is making very strange and very opinionated decisions far too often for my liking. It's really making me second guess my continued use of Claude Code.
> I consider my prompts and prompting style to be trade secrets. No one wrote this with a straight face did they?
Re: Claude Session URL appended to commit messages and PR descriptions by default
#183I really hate this attribution nonsense ... On one hand I guess it is fine to automatically tag that the commit was AI-generated. On the other hand, this will happen even if you audit every line and add your own changes too, which means the attribution is misleading.
Having only 1 of the token sellers do this is not very helpful either. Its just free branding & advertising for Misanthropic.
How have I not heard this one before
Re: Claude Session URL appended to commit messages and PR descriptions by default
#184The major problem I see with these are linkrot. Do any of us truly believe these links will work 30 years from now? Post IPO, many years down the line, a leadership that is eager to cut costs will look at their storage usage and expire 7 year old non-training sessions. Quickest thing to go. I have zero faith in any successful provider getting this right. Git is supposed to be the durable storage medium, self containi…
That said, I wouldn't agree with using the session URL as the entire commit message, or even with letting the session URL make up for other missing details. But to me it's an at-worst neutral change to add it to an otherwise acceptable commit message.
Re: Claude Session URL appended to commit messages and PR descriptions by default
#185I don't see any issue with this at all. I noticed it the other day and thought it was convenient. The same way I let the agent tag the PRs/commits with its name. I want to know what was used, in fact I wish it would identify the model used. I'm not embarrassed by my LLM usage and I want to provide a full audit trail whenever possible to aid myself in the future. PS: Claude archives old conversations on your computer…
Does adding this to your Claude settings.json not work anymore?
{ "cleanupPeriodDays": 99999 }
Re: Claude Session URL appended to commit messages and PR descriptions by default
#186I can't believe how many people are in favor of it. Like it's so positive in the comments I'd think it's astroturfing. The code is the result of my work however it got done, and if I don't document or explain it well enough then that's a separate issue. Did you want to see my slack messages to my mentor too? Or how about all the stack overflows I read? Maybe I should voice record all the times I swore about Gary the…
100% agree with this. Want my browser search history too so you can see my thought process? This is terrible. I have no desire to read your Claude conversation. I don’t even want to read mine if I do use Claude. The code is the artifact. There’s no value in trying to make the noisy, verbose conversation one. It’ll likely be dead in future years anyway.
If the code is artisan to any degree (authored, edited, reviewed, etc.), it's a bit ridiculous.
It does makes sense to me if the human driver was hands-off the code because the conversation becomes the artifact.
I'm older, and have very mixed feelings about the latter case but it seems inevitable that engineers will be working at a higher level where conversational governance becomes important. We'll stop this charade of hiding AI contributions behind human identities. (Note: I don't think conversation IDs are what we need but it's a step down this path.)
Re: Claude Session URL appended to commit messages and PR descriptions by default
#187Earlier quoted context omitted.
Same here, cool, now Claude can grab the context from the session to reason better about why things are the way they are. Maybe an ID alone would have been better, not a whole http url.
It feels like an absolute failure of project management if your tooling needs to attach a session identifier in a git commit message for it to understand what’s going on. Wikis, changelogs, decision records, issue trackers and more are available to provide greater context for you, your team and the agents you deploy.
Re: Claude Session URL appended to commit messages and PR descriptions by default
#188Earlier quoted context omitted.
Funny to compare it to “Sent from iPhone” that Apple appended to emails by default way back when. It was an ad, but nobody cared because using iPhone was a point of pride.
I cared. Deleting that constantly was pretty annoying. And why would I have pride in whatever device I’m using?
Re: Claude Session URL appended to commit messages and PR descriptions by default
#189I can't believe how many people are in favor of it. Like it's so positive in the comments I'd think it's astroturfing. The code is the result of my work however it got done, and if I don't document or explain it well enough then that's a separate issue. Did you want to see my slack messages to my mentor too? Or how about all the stack overflows I read? Maybe I should voice record all the times I swore about Gary the…
Re: Claude Session URL appended to commit messages and PR descriptions by default
#190I may be missing something, but this is exactly what I want as a default. I want the session links there. I see PRs from my coworkers with session links. I still get to control whether other people can see the session, but I don’t lose it. I don’t get the “unprofessional” argument. This is attribution. Attribution is professional. If you don’t want it, you turn it off or rewrite the commit messages. If you are having…
as for the commit message: if it's the usual verbose Claude style, I'm also not going to read it. to be honest, probably if it's not verbose, I'm still not reading it.
I'll ask my review agent anyway to summarize your code. My review agent will read your commit message.