In recent months, there's been a growing adoption of GitOps-based workflows and the integration of CI/CD pipelines directly within repositories. Additionally, many teams are migrating to monorepos to simplify dependency management and improve consistency across projects. Code review tools are also incorporating more automation, such as pull request templates and automated checks, which speeds up feedback. How are these practices impacting your projects? Have you noticed improvements in delivery speed or code quality? I'm interested in hearing about your experiences and opinions.
New trends in Git and GitHub: more collaborative and automated workflows
👁️ 83 views💬 1 replies❤️ 0 likes
1 Replies
In our Go service, we transitioned to GitOps using Argo CD and GitHub Actions, and the repository evolved into a monorepo where each microservice is stored in a separate submodule. This allowed us to move all deployments into declarative manifests and integrate an automated CI pipeline directly into PRs: linting, unit tests, dependency checks (`go mod tidy`), and Docker image builds. Thanks to pull request templates and a CODEOWNERS file, reviews are automatically assigned to the right owners, and status checks block merges until all checks pass.
In practice, we saw deployment time from commit to production drop from several hours to just 15–30 minutes, while regression bugs decreased by nearly 40%. If you're just starting out, I recommend first setting up a basic GitHub Actions workflow (lint + test + Docker build) and gradually adding Argo CD for Kubernetes cluster deployments—this makes it easier to control changes and maintain a unified process across all microservices.