Search for a command to run...
I’m the founder and CEO of Okteto, where we’re busy re-imagining the developer experience for cloud native applications.
Before Okteto, I built enterprise chat products at Atlassian, application lifecycle management tools at Elasticbox (now part of Centurylink) and cloud services at Microsoft Azure.
No comments yet. Be the first to comment.
https://www.youtube.com/watch?v=tcgQyrkS7Qs he bottleneck for AI in software development isn't smarter models. It's giving agents a real place to run. Back on The Software Plaza with Twain Taylor f
Platform Engineering Day North America 2026
KCD San Francisco Bay Area 2025
Earlier today, I had the privilege of speaking with a group of young entrepreneurs through the 3percentclub , an organization dedicated to increasing diversity in tech by providing underrepresented talent with accessible education. My friend Maria As...
Platform Engineering Day Europe 2025
The other night I realized that I had being commiting to one of my personal open source projects using an email that I no longer use. I had being doing this for a while without noticing, until I enabled gpg signing on my github repos. At that point, github realized that the email I had configured on git didn't match the key it was expected, and didn't let me commit anymore. It took me some time to figure out what was going on, until I looked at my local git history and realized that I had the old email (facepalm).
Once I realized the issue, I fixed my email cofiguration and it was all good. But my commit history looked messy, so I decided to fix it.
git filter-branch lets you to rewrite your commit history, and it has a very powerful filtering system that lets you script your conditions. After searching online, and a bit of trial and error, I ran into this. I'm putting the script here for future reference.
git filter-branch -f --env-filter '
OLD_EMAIL="old@example.com"
CORRECT_EMAIL="new@example.com"
if [ "$GIT_AUTHOR_EMAIL" = "$OLD_EMAIL" ]
then
export GIT_AUTHOR_EMAIL="$CORRECT_EMAIL"
fi
if [ "$GIT_COMMITTER_EMAIL" = "$OLD_EMAIL" ]
then
export GIT_COMMITTER_EMAIL="$CORRECT_EMAIL"
fi
'
When you run this script, git will go over every commit, compare the author, and fix it if needed. After you're done, review your history, and if you're happy with it, force push your changes (since you're and you're all done.
I ended up making this a bit more generic, and adding it as a git alias for future use on my ~/.gitconfig:
[alias]
change-commits = "!fix() { var=$1; old=$2; new=$3; shift 3; git filter-branch --env-filter \"if [[ \\\"$`echo $var`\\\" = '$old' ]]; then export $var='$new'; fi\" $@; }; fix"
Do keep in mind that this script is changing your commit history, so DO NOT RUN THIS ON A SHARED REPOSITORY, unless you really know what you are doing.
Hope it helps!