Best of Git — September 2024
- 1
- 2
Code Like A Girl·2y
Mastering Git: Hidden Commands Every Developer Should Know
Git offers several hidden commands beyond the commonly used ones. Commands like git stash, git reflog, git bisect, git cherry-pick, git reset --hard, git blame, git clean, and git shortlog can significantly enhance your version control skills. These commands help in temporary save uncommitted changes, recover lost commits, identify problematic commits, selectively apply commits, reset code to a specific commit, track changes to specific lines, clean up untracked files, and summarize contributions by author.
- 3
Coding in Public·2y
My new favorite way to use git
Git is a powerful tool with a steep learning curve, especially when using the command line interface. Lazy Git offers a graphical interface within the CLI, making it easier to manage Git tasks without memorizing commands. The post discusses the installation on Mac OS via Homebrew and showcases basic functionalities like staging, committing, and stashing changes. It emphasizes the speed and efficiency Lazy Git brings to the table for developers.
- 4
DEV·2y
GitHub Foundations certification is free! 🚀🔥💲
GitHub Foundations certification exam is now free for verified students on GitHub Education. Previously costing $99, this offer requires students to register with a school-issued email and enable two-factor authentication on their GitHub account. The exam covers GitHub basics, including repositories, commits, and project management. Upon passing, students receive a Credly badge as digital proof of their achievements.
- 5
Faun·2y
A Guide to Git Branching Strategies
Source control management is crucial for efficient collaboration and versioning in software development. This guide focuses on Git branching strategies, primarily trunk-based development and Gitflow. Trunk-based development facilitates fast integration and deployment using a single long-lived branch, while Gitflow supports parallel development and is ideal for established products with regular release cycles. Understanding these strategies helps teams choose the best workflow based on their size, experience, and deployment needs.
- 6
Adam Johnson·2y
Git: avoid reset --hard, use reset --keep instead
When undoing commits in Git, it's recommended to use 'git reset --keep' instead of 'git reset --hard' to avoid losing uncommitted changes. 'reset --hard' is highly destructive as it discards unsaved work, making recovery difficult. In contrast, 'reset --keep' preserves uncommitted changes and fails if it jeopardizes unsaved work. The post provides practical examples and suggests setting an alias for convenience.
- 7
Community Picks·2y
GitKraken Legendary Git Tools
GitKraken offers a suite of tools designed to streamline Git management for developers, enabling better visualization of complex data, improved focus, and effective collaboration. It's built for teams of all sizes and integrates seamlessly with popular platforms like GitHub, GitLab, and Jira. The platform helps reduce distractions and interruptions, making it easier to manage tasks and maintain context. GitKraken improves developer productivity with features like the Commit Graph and Workspaces for multi-repo actions and onboarding.
- 8
Visual Studio Code·2y
The easiest way to visualize your repo
Discusses two methods for visualizing a repository history: the git log graph command and VS Code’s built-in Source Control graph. The author finds the VS Code method more intuitive, as it allows easy scrolling through history, viewing branching structures, and inspecting individual commits.
- 9
Unlisted GitHub Repositories
Creating unlisted repositories on GitHub can be accomplished by using a public host repository with multiple branches, each representing a different unlisted repository. This approach prevents clutter on your profile and allows for sharing complex code snippets or reproducing issues without creating new repositories. The process can be streamlined with scripts and git aliases, though it has limitations like the inability to support multiple branches, issues, or pull requests.
- 10
This is Learning·2y
Style guide to write git history
This guide provides a structured approach to writing maintainable Git history. It categorizes commit messages with prefixes like 'feat', 'chore', 'refactor', 'deploy', and 'docs' to clearly indicate the type of change. For large features, it recommends dividing branches into smaller modules using numerical suffixes. Key general practices include creating PRs, consistent naming, using present tense in commit messages, and utilizing squash merges when appropriate.
- 11
gitme·2y
Learn Git and GitHub with Me: A Beginner's Guide "Dive into the world of version control with Git and GitHub. This blog post provides a step-by-step guide for beginners to understand and use Git and GitHub effectively."
This beginner's guide provides a comprehensive introduction to Git and GitHub, explaining essential concepts and basic commands to help newcomers get started with version control.