Building an automated release branch sync tool with Bash
once a release branch is fork from trunk, every hotfix over the next week or two must be cherry-picked back to the release branch, that's a problem
once a release branch is fork from trunk, every hotfix over the next week or two must be cherry-picked back to the release branch, that's a problem
Noticed friction when committing Go code (tabs, alignment, minor formatting). Moving native Go static checks to CI enforces consistent formatting.
Self-hosting Lighthouse allows for long-term tracking of best practices. As it enhances the team's awareness regarding code quality over time.
The website's content are recorded in Git. This decision has its pros and cons, As the project matures, I've decided to separate the two.
When using packages, one often wonders about the general process of managing package development. So I write the process of publish a TS package