With more developers working remotely, traditional code reviews have begun to shift. Classic water cooler conversations have turned into pings on Slack, and collaborative office spaces have transformed into stand-alone home setups. Remote work clearly has many advantages, but it can also leave developers feeling isolated. Asynchronous communication introduces massive bottlenecks for efficient feedback and creative brainstorming, particularly during code reviews.

In part one of this series, we covered how you could limit deployments to Platform.sh only when a tag is pushed/created, focusing primarily on using GitHub and the GitHub Actions platform to accomplish this goal. But we’re a polyglot PaaS and strive to be agnostic in our users’ source code management terms of the service. With that in mind, let’s look at how we can accomplish the same goal using GitLab and your CI/CD system. Just like last time, there are some assumptions to consider.

Monitoring your identity provider’s logs is critical to identify potential security threats. These logs are vital for a security team, who may store them in a specialized tool like Grafana Loki for enhanced accessibility and analysis. The ability to pinpoint specific patterns within these logs is key — and by crafting these patterns into Loki queries, you can conduct focused searches across logs.