Git: Guides and Practical Know-how | Page 9 | mironsoft Blog
Git
-
Sep 7, 2025
No other part of a zero downtime deployment fails as often as database migrations. Renaming a column, dropping a table, adding a NOT NULL constraint: these are operations that are simply not compatible with code that is still running. This article explains the expand/contract pattern, when it works, and when a maintenance window is the more honest answer.
-
Sep 4, 2025
A good commit message explains why a change was necessary, not just what changed in the code, since the diff already shows that. With the 50/72 rule, an imperative subject line, clean trailers for ticket references, and optionally Conventional Commits, the Git history becomes a searchable archive that significantly speeds up debugging and code archaeology months later.
-
Sep 3, 2025
Who deployed what to production, and when? In e-commerce, that's not an academic question, it's a compliance requirement. GitLab provides the tools to make deployments traceable, from audit logs through protected branches to enforced review processes.
-
Sep 1, 2025
A generic code review misses the traps that specifically cause production problems in Magento: misused preferences, broken public APIs, install scripts instead of schema. A Magento-specific code review checklist surfaces these risks systematically before they get merged.
-
Aug 29, 2025
Inconsistent code isn't born of ill will, it's born of missing tooling. EditorConfig, PHP CS Fixer and PhpStorm inspections together enforce consistent code automatically, with no discussions needed in code review.
-
Aug 29, 2025
A repository that has grown over years usually contains a fair number of large binary files that would have been better off in Git LFS from the start. git lfs migrate import can fix that retroactively, but only if history rewriting, team coordination, and the force push are planned carefully.
-
Aug 24, 2025
Zero downtime deployments do not fail because of the pipeline, they fail because of a badly prepared server structure. If shared directories and symlinks are not set up correctly, every release either loses media files or loses the configuration.
-
Aug 21, 2025
By default, PHPStorm shows so many inspection warnings that developers collectively start ignoring them. That is counterproductive: warnings lose their signal value and real problems get lost in the noise. The solution is not less quality assurance, but smarter configuration.
-
Aug 21, 2025
Without clear repository governance, even well-written pipelines are organizationally fragile. Projects, groups, access roles, and protected branches form the foundation on which secure Magento deployment pipelines can be built.
-
Aug 16, 2025
Many teams treat git blame as a tool for pointing fingers, when in reality it delivers valuable context: who changed a line, when, and why. This article shows practically how to get sharper results with flags like -w, -C, and -M, cleanly exclude mass reformatting commits, and correctly read blame output in both PhpStorm and the command line.