/explore
|
You are here 
|
smsohan.com | ||
| | | | |
notes.ghinda.com
|
|
| | | | | I've been using git worktree for at least five years now. Here's how I set things up at work. Say I work on `short_ruby` project. I create a folder called `short_ruby` and inside I have: `short_ruby/main` -> which will always remain as head main `short_ruby/pairing` is where I pull branches for code reviews, dig deeper into changes, or show draft code to a colleague. `short_ruby/feature_` is a new worktree I create for each feature I work on, and I remove it when I'm done. Why these folders: 1. I always keep a local copy of the current main branch. This helps me review changes or start something new, since I can quickly check how production works if main is what's deployed. 2. I also want to quickly access any branch I'm reviewing, while still being able to ... | |
| | | | |
pombomailer.com
|
|
| | | | | ||
| | | | |
www.useragentman.com
|
|
| | | | | [AI summary] The blog post discusses accessibility coding best practices for web developers, offering open-source resources and community input. | |
| | | | |
hiltmon.com
|
|
| | | |||
