Browse all posts by tag

tbdflow ❤️ monorepo

Monorepos are a powerful strategy for managing code. By keeping all your projects in a single repository, you get a single source of truth, simplified dependency management, and easier cross-team collaboration. As influencial thought-leaders and others in the DevOps space have pointed out, monorepos are a natural fit for Trunk-Based Development (TBD) because they both revolve around a single, shared mainline of code.

Read more...

Looking under the hood with a dry-run

One of the most valuable pieces of feedback I’ve had about tbdflow came as a simple question:

Read more...

CHANGELOG.md

I’ve seen some teams and projects having really nice CHANGELOG.md and release notes but knowing from experience, writing release notes by hand is a pain. Scrolling through git log, guessing which commits count as features or fixes, and hoping you don’t forget something important isn’t exactly fun.

Read more...

How I created the demo GIF for tbdflow

All projects need a good README.md, It’s the front door to the project and it needs to quickly show a potential user what the tool does and why it’s valuable. I put a lot of effort in having a good README for tbdflow but it was still static text, and the examples was buried deep down.

Read more...

Why did I build medi?

Where are my files?

Read more...