The-Strategy-Unit / The-Strategy-Unit/data_science
Blog post about tools and ways to avoid git pickles
@ai-mindset is already working on this.
Since Dec 9, 2025.
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
Git is very useful but not the most intuitive or the easiest tool to use. Furthermore, the code review -> address comments -> approve PR -> merge cycle may take longer depending on the team's workload.
Given we are always on the lookout for more efficient workflows, it's be useful to document our findings on how we avoid merge conflicts, messy git history and so on. We recently came across https://www.git-town.com/. It might be worth documenting our experience with this tool as a way of keeping a cleaner and less error-prone git workflow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.