Join us

ContentUpdates and recent posts about git..
Discovery IconThat's all about @git โ€” explore more posts below...
Story
@laura_garcia shared a post, 6ย hours ago
Software Developer, RELIANOID

๐— ๐—ช๐—– ๐Ÿฎ๐Ÿฌ๐Ÿฎ๐Ÿฒ: ๐—Ÿ๐—ฒ๐˜€๐˜€๐—ผ๐—ป๐˜€ ๐—น๐—ฒ๐—ฎ๐—ฟ๐—ป๐—ฒ๐—ฑ ๐—ณ๐—ผ๐—ฟ ๐—ฎ๐—ฝ๐—ฝ๐—น๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป ๐—ฑ๐—ฒ๐—น๐—ถ๐˜ƒ๐—ฒ๐—ฟ๐˜† & ๐˜€๐—ฒ๐—ฐ๐˜‚๐—ฟ๐—ถ๐˜๐˜†

๐Ÿ”ต ๐— ๐—ช๐—– ๐Ÿฎ๐Ÿฌ๐Ÿฎ๐Ÿฒ: ๐—Ÿ๐—ฒ๐˜€๐˜€๐—ผ๐—ป๐˜€ ๐—น๐—ฒ๐—ฎ๐—ฟ๐—ป๐—ฒ๐—ฑ ๐—ณ๐—ผ๐—ฟ ๐—ฎ๐—ฝ๐—ฝ๐—น๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป ๐—ฑ๐—ฒ๐—น๐—ถ๐˜ƒ๐—ฒ๐—ฟ๐˜† & ๐˜€๐—ฒ๐—ฐ๐˜‚๐—ฟ๐—ถ๐˜๐˜† After an intense week in Barcelona, one thing is clear: ๐Ÿ‘‰ The future is not just about connectivityโ€ฆ itโ€™s about ๐—ต๐—ผ๐˜„ ๐—ฎ๐—ฝ๐—ฝ๐—น๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป๐˜€ ๐—ฎ๐—ฟ๐—ฒ ๐—ฑ๐—ฒ๐—น๐—ถ๐˜ƒ๐—ฒ๐—ฟ๐—ฒ๐—ฑ, ๐˜€๐—ฒ๐—ฐ๐˜‚๐—ฟ๐—ฒ๐—ฑ, ๐—ฎ๐—ป๐—ฑ ๐—ฐ๐—ผ๐—ป๐˜๐—ฟ๐—ผ๐—น๐—น๐—ฒ๐—ฑ ๐Ÿš€ Key takeaways ๐Ÿญ. ๐—”๐—œ ๐—ถ๐˜€ ๐—ป๐—ผ๐˜„ ๐—ถ๐—ป๐—ณ๐—ฟ๐—ฎ๐˜€๐˜๐—ฟ๐˜‚๐—ฐ๐˜๐˜‚๐—ฟ๐—ฒ AI-driven networks are h..

MWC26_relianoid_recap
Story
@laura_garcia shared a post, 1ย day, 3ย hours ago
Software Developer, RELIANOID

Retailers invest millions in digital experiencesโ€ฆ

but what happens when the checkout stops working? A recent outage affecting the online services of Tesco has once again sparked an important discussion: how resilient are modern retail platforms? Customers reported failures during some of the most critical moments of the shopping journey: - Checkout..

tesco outage
Link
@hamzmu shared a link, 1ย day, 11ย hours ago
Fellow, Rootly

On-Call Burnout: What Incident Data Doesnโ€™t Show

Incident dashboards measure system health, but rarely show the workload and strain engineers face when responding to alerts. Incident load isnโ€™t only about the number of incidents, but the patterns surrounding them. In this article we explore these patterns and introduce On-Call Health, an open-source tool that analyzes engineering signals to surface early burnout trends, highlighting why incident volume alone isnโ€™t enough and why after-hours interruptions, workload stacking, and long-term trends matter.

https___dev-to-uploads.s3.amazonaws.com_uploads_articles_nv7wk3k0nzlublr1nm43
ย Activity
@sagar0041 started using tool Jenkins , 2ย days, 23ย hours ago.
ย Activity
@sagar0041 started using tool Kubernetes Dashboard , 2ย days, 23ย hours ago.
ย Activity
@ishanupadhyay started using tool Jenkins , 3ย days, 6ย hours ago.
ย Activity
@ishanupadhyay started using tool Azure Pipelines , 3ย days, 6ย hours ago.
ย Activity
@ishanupadhyay started using tool Terragrunt , 3ย days, 6ย hours ago.
ย Activity
@ishanupadhyay started using tool Terraform , 3ย days, 6ย hours ago.
ย Activity
@ishanupadhyay started using tool Sonatype Nexus , 3ย days, 6ย hours ago.
At its core, Git records snapshots of state, not just file diffs. Every commit represents a complete, immutable view of the project at a point in time, identified by a cryptographic hash. This makes history reliable, auditable, and cheap to branch.

Git is distributed by design. Every clone contains the full repository history, which allows developers and automation systems to work offline, create branches freely, and synchronize changes without relying on a central server for every operation.

In modern cloud-native workflows, Git acts as the source of truth. Desired state is declared in Git, reviewed through pull requests, and promoted across environments by merging changes rather than applying ad-hoc commands. This is the foundation of GitOps.

Git does not deploy anything by itself. Its role is to capture intent, history, and collaboration, while other tools turn that intent into running systems.