EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·Jul 31·5 min read
Accepting a messy git history
TL;DR
GitHub's introduction of stacked pull requests has sparked a debate between two types of Git users: those who prefer a clean, rebased history and those who embrace a more chaotic, commit-often approach. Each group believes their method better reflects the development process.
✦ Why It Matters
Evaluate your team's Git practices to align on a preferred commit strategy that suits your workflow.
Key Takeaways
- Evaluate your team's workflow to determine the best Git practices.
- Balance between clean history and realistic development representation.
- Communicate merging strategies to avoid conflicts in commit preferences.
- Be open to adapting your approach as team dynamics change.
Full Summary
The recent release of stacked pull requests on GitHub has ignited discussions among developers about their Git workflows. Two distinct groups have emerged: those who commit often and view the rebase process as unnecessary, and those who prioritize a clean commit history through careful rebasing.
Proponents of frequent commits argue that a detailed history reflects the actual development process, while advocates for clean histories believe it clarifies the intent behind changes. The debate extends to merging practices, with rebase supporters opposing squash merges that simplify history at the cost of losing individual commits.
Ultimately, the article suggests that while a clean history is ideal, the practicalities of larger teams may lead to a more chaotic Git history being the norm. This reflects a broader acceptance of messy histories in collaborative environments.