Best of GitJuly 2024

  1. 1
    Article
    Avatar of devtoDEV·2y

    Good Commit ✔ VS. Bad Commit ❌: Best Practices for Git

    Good commits are crucial for maintaining a clean and understandable project history in Git. Characteristics of good commits include being atomic and focused, having descriptive messages, following conventional guidelines, being tested and verified, and being properly scoped. Conversely, bad commits are large and unfocused, have vague or misleading messages, combine unrelated changes, and contain incomplete or untested code. Best practices for good commits involve committing often but meaningfully, writing clear messages, using branches effectively, reviewing and squashing commits, and automating testing.

  2. 2
    Article
    Avatar of communityCommunity Picks·2y

    Git Commands for Software Engineers

    Git is a crucial tool for software engineers that supports efficient version control and collaboration. Mastering Git commands helps streamline development workflows. This guide covers important commands such as git config, git init, git commit, git push, git pull, git branch, git merge, and many others that are essential for managing codebases and coordinating with team members.

  3. 3
    Article
    Avatar of engineerscodexEngineer’s Codex·2y

    Good programmers worry about data structures and their relationships

    Good programmers focus on designing robust data structures and understanding their relationships, as emphasized by Linus Torvalds, the creator of Git and Linux. This approach makes software more reliable, easy to maintain, and scalable. Complex systems benefit greatly from well-thought-out data models, which simplify application logic and reduce the need for complex code. Prioritizing data structure design saves time and effort in the long run.

  4. 4
    Article
    Avatar of javarevisitedJavarevisited·2y

    How to use Git Stash like a professional

    Learn how to use git stash to manage your unfinished code when encountering urgent tasks or bugs. This guide covers the basics of the working directory, staging area, and local repository, detailing commands such as git stash save, git stash apply, and git stash pop to temporarily store and retrieve code changes efficiently.

  5. 5
    Article
    Avatar of communityCommunity Picks·2y

    A complete guide to open source - 100x simpler

    The post provides a comprehensive guide to getting started with open source, covering essential concepts, benefits, and various roles in open-source projects. It offers practical advice on contributing, including for non-coders, details pre-requisites like Git, GitHub, and Markdown, and explains conventions like conventional commits. Additionally, it underscores the importance of guidelines, legal aspects, and ways to effectively find and contribute to good projects.

  6. 6
    Article
    Avatar of communityCommunity Picks·2y

    Boost Productivity with Git Worktrees

    Git worktrees allow you to manage multiple working trees attached to the same repository, enabling you to have multiple commits checked out simultaneously. This tool is especially useful when working on different branches or pivoting between tasks without re-installing dependencies. Worktrees maintain their own state, including dependencies and editor states. For better workflow, tools like 'better-commits' can optimize common operations, ensuring dependencies are installed and branches are created efficiently.

  7. 7
    Article
    Avatar of scottloweScott's Weblog·2y

    Using a Git Commit Template

    The post discusses the benefits and process of using a Git commit template, inspired by the Conventional Commits specification. A Git commit template helps to ensure consistency and build good habits in commit messages. The process involves creating a template file and configuring Git to use it, which can be done across various platforms like macOS, Linux, and Windows. This functionality is available directly from the terminal, although it can also be found in graphical Git clients like Tower.

  8. 8
    Article
    Avatar of freecodecampfreeCodeCamp·2y

    How to Improve Your JavaScript Code with Powerful Build Tool Configs

    This post details how to improve JavaScript code quality using configuration tools like ESLint, Prettier, and Git hooks. It covers the setup and usage of these tools to enforce coding conventions, enhance code readability, and enforce pre-commit checks for secrets and unit test failures. The author, with over 6 years of frontend development experience, shares how these configurations can streamline development workflows and ensure code consistency across teams. Practical examples and setup instructions are provided for a hands-on understanding.

  9. 9
    Article
    Avatar of frontendmastersFrontend Masters·2y

    Lazygit – Frontend Masters Boost

    Lazygit offers a Terminal User Interface (TUI) for Git, combining the benefits of command-line and graphical user interfaces. While traditionally a GUI user, the author is exploring Lazygit as an intriguing middle ground. For those interested in creating TUIs, Charm.sh provides impressive tools.

  10. 10
    Article
    Avatar of webtoolsweeklyWeb Tools Weekly·2y

    JavaScript Libraries, Testing Tools, Git/CLI

    Issue #574 of Bytes covers a wide range of JavaScript topics including libraries such as Rezact, Bridge, and Flitter, testing tools like screen-scaler and Quickboot.js, and Git/CLI tools such as git-cliff and concurrently. The newsletter also includes commercial apps and services, and a call to action for developers to share tools they've created.

  11. 11
    Article
    Avatar of communityCommunity Picks·2y

    A Git story: Not so fun this time

    The post traces the development of Git, starting with Linus Torvalds's struggle to manage the growing complexity of Linux kernel development. This leads to the introduction of BitKeeper by Larry McVoy. Despite initial success, its restrictive licensing eventually prompted Linus to create Git. The post highlights contributors like Junio Hamano and the role GitHub played in Git's adoption and evolution. It underscores how Git's simplicity, coupled with community contributions, established it as the dominant version control system.