Git: Guides and Practical Know-how | Page 13 | mironsoft Blog
Git
-
Apr 30, 2025
A single accidental commit containing database credentials or the crypt key from app/etc/env.php can compromise an entire Magento project, even after the repository is later set back to private. This article explains which files must never end up in Git, what a clean gitignore baseline looks like, and how a secrets manager and pre commit scanning reliably prevent it.
-
Apr 28, 2025
Not every environment has direct network access to a Git server, whether due to security constraints inside isolated networks or simply the lack of an internet connection. Git bundle packs commits, trees, and blobs into a single file that can be passed along via USB stick, email, or any other transport channel and hooked up like a regular remote.
-
Apr 28, 2025
A raw diff output is technically complete but hard to read in a terminal, because lines marked with plus and minus barely stand out visually. This article shows how colored diff output emerges in Bash scripts, from ready-made tools like colordiff and git diff to your own ANSI coloring with awk for edge cases no standard tool covers.
-
Apr 27, 2025
Anyone can set git config user.name and user.email to any value and create commits that appear to come from a colleague, without Git preventing it. This article shows how GPG- and SSH-based commit signatures cryptographically prove who actually created a commit, how to set up keys, verify signatures, and enforce signed commits across a team through branch protection rules.
-
Apr 21, 2025
PhpStorm's remote host integration with automatic SFTP upload is powerful, and dangerous if used the wrong way. This article explains which scenarios the feature is built for, where its limits lie, and at what project size a Git-based CI/CD pipeline becomes the clearly better choice.
-
Apr 20, 2025
A good changelog generator reads the commit history, recognizes the type and scope of every change, and builds a structured CHANGELOG.md from it, with no manual editing required. This article shows how such a changelog generator can be built as a plain Bash script, what pitfalls appear when parsing Conventional Commits, and how the result plugs cleanly into a release pipeline.
-
Apr 15, 2025
In monorepos with thousands of directories, a full checkout quickly becomes a burden on disk space, checkout time, and IDE indexing. Git sparse checkout lets you materialize only the directories you actually work with in the working directory, while the full history stays available in the repository.
-
Apr 15, 2025
A deployment that's considered successful right after the symlink switch hasn't actually concluded on a functional level. Post-deploy checks make the difference between a pipeline that ends technically and a pipeline that confirms the application actually works.
-
Apr 15, 2025
Cache speeds up builds by reusing download results. Artifacts carry built results between jobs. Anyone who confuses the two ends up fighting inconsistent builds, needlessly long pipeline runtimes, and Magento deployment artifacts that are hard to reproduce.
-
Apr 10, 2025
A single large formatting commit is enough to make git blame useless for an entire file, since every line suddenly points to that one commit instead of the actual functional change. The .git-blame-ignore-revs file solves exactly this problem without touching the commit history itself.