From: Alex Williams <alex@williamstechcopy.com>
To: git@vger.kernel.org
Subject: Content idea for Git
Date: Thu, 06 Aug 2026 13:04:03 +0000 [thread overview]
Message-ID: <019fd72c-60b0-74b8-8db0-22a9a2148b6a@williamstechcopy.com> (raw)
Hello Team,
I noticed Git's blog hasn't covered AI coding agents in developer workflows yet: Teams are wiring AI agents into commits, reviews, and CI, but most coverage stays theoretical instead of walking through the setup.. It's a topic your readers are actively looking for.
I'm Alex Williams, a full-stack developer turned technical writer (MSc Computer Science, University of London), cited by TechTarget, PhoenixNAP, RavenDB, and ProgrammableWeb. Recent work includes pieces like "Goodhart's Law Comes for Every Benchmark You Trust" and "Why the Frontend Should Embrace Platform Engineering."
I'd like to write Git a grounded, source-backed post on How AI coding agents fit into the modern dev workflow at Git.
Can I send over two or three headline concepts this week?
Best,
Alex Williams
williamstechcopy.com | linkedin.com/in/alexwilliams1337 //linkedin.com/in/alexwilliams1337
P.S. Kindly reply with "no thanks" if you would prefer not to hear from me again
reply other threads:[~2026-08-06 13:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=019fd72c-60b0-74b8-8db0-22a9a2148b6a@williamstechcopy.com \
--to=alex@williamstechcopy.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox