129
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Sep 2023
129 points (93.9% liked)
Programming
17314 readers
138 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Vscode and git lens. If you are older like me, emacs and magit
Unfortunately, GitLens is by GitKraken. Seems like they might not restrict it for private repos, though, I'll check it out.
They dont restrict it, I use it with private repos all the time
Isn't there a magit-alike plugin for vscode? I have found it so frustrating working with devs who don't use magit, because most seem to find slightly more advanced git like squash and fixup and cherry picking to be impossibly hard.
For these reasons, I always push for simple and straightforward workflows and many commits and merges. For many people git remains a mistery also after years working on it. I blame the easy-to-use guis, many people learn 2 buttons to press for a workflow, and they never care learning more
All the people I've worked with seem to use the command line. They just don't know much beyond "commit everything" and basic push/pull/branch/merge.
Conversely I learned most of what they don't know direct from the magit GUI. So I often don't know the specific command arguments. Not a good thing, but only a problem for communicating what to do to others.
Magit is super cool but not exactly easy to use :D
This^ plus ungit (especially when things go really bad; e.g. force pull/push) seems to be the current ideal git workflow.
Hopefully this project will change that though!