Jerry Nixon gives 'A Developer's Guide to Database Patterns' July 24th at Nebraska.Code().
Jerry Nixon gives 'A Developer's Guide to Database Patterns' July 24th at Nebraska.Code().
Any alternative recommendations for free Git hosting? Does Github still work with ICE? Is GitLab any better? Am I asking too much and should just self-host? Is it feasible to stand up a git server at home and expose it to the outside world if I don't have a static ip address? What's the airspeed velocity of an unladen swallow?
Boost your GitHub productivity with Visual Studio's new multi-account support.
buff.ly/OzS3b6h
#visualstudio #github #productivity #sourcecontrol #vs2022
Boost your GitHub productivity...
Boost your GitHub productivity with Visual Studio's new multi-account support.
Spent yesterday afternoon fixing an issue with #aquaplane controls, somehow messed up a source control merge, decided to start again ...then realised I hadn't committed my changes for a while so had to do the work on that branch again. #gamedev #indiedev #love2d #sourcecontrol
Today on #SystemCrafters Live, we'll take a look at `jj` (Jujutsu), an interesting distributed version control system that intends to be more user-friendly than Git while having even more advanced features.
Can `jj` be a good replacement for Git in the long term? Let's find out!
Join us here:
- https://youtube.com/live/zej0A21PJyc
- https://twitch.tv/SystemCrafters
- https://systemcrafters.net/live
in your time zone: https://time.is/compare/1800_in_Athens
Last year, a colleague introduced me to lazygit, a TUI git client with a wealth of value-added features.
Somehow, though, my favourite feature is the animation you see if you nuke the working tree. Excellent.
Introducing the Copy Git Permalink Feature in Visual Studio 17.12.
https://buff.ly/3CZDXWo
#visualstudio #git #productivity #sourcecontrol #vs2022
Naive Git-based development etiquette/practices/whatever question. Say you want to point someone to a file that you'd like them to update. You're most likely to give them:
Realizing now that I "learned" source control practices at FB and Google for 10+ years, and they almost exclusively use "trunk based development". Now that I'm at a place that does not do that, there are pitfalls I don't always think about.
Like, talking through a data storage idea I had today, my teammate said, "Yes, except for branches." And I was like...oh, right.