Either the agent doesn't fully understand perforce (who does?) or our setup of perforce is so divergent from "standard" who even knows anymore...
Either the agent doesn't fully understand perforce (who does?) or our setup of perforce is so divergent from "standard" who even knows anymore...
Version Control for Solo Devs with Git & GitHub—no terminal.
➡️ Enroll Now: https://bit.ly/3KFtxir
#UnrealEngine #GameDev #IndieDev #solodev #udemy #UE5 #git #github #versioncontrol #revisioncontrol #sourcecontrol
GitHub CEO: Embrace AI or get out.
https://www.businessinsider.com/github-ceo-developers-embrace-ai-or-get-out-2025-8
PS. Here’s where to go: @Codeberg
(As an additional bonus, you’ll have the peace of mind of knowing you’re part of an anti-fascist not-for-profit cooperative instead of a trillion-dollar US corporation that’s helping Israel commit genocide.)
#git #sourceControl #revisionControl #GitHub #Codeberg #dev #AI #BigTech #Microsoft #israel #genocide #ethnicCleansing #apartheid #settlerColonialism #Palestine #StopIsrael #StopArmingIsrael #StopTheGenocide #FreePalestine
Git revert tango (one step forward, one step back).
My personal record is
Revert ³ <commit message>
("what I tell you three times is true").
I note that when Git does
<message> → Revert "<message>"
for the draft commit message, it doesn't escape nested double quotes in the message.
I'm shocked 🙂.
Linux Fu: Deep Git Rebasing
#hackadaycolumns #linuxhacks #softwaredevelopment #git #linuxfu #rebase #revisioncontrol #tips #hackaday
-- Delivered by RssEverything service
I am fairly new to using Git with multiple engineers. Can someone tell me, if I do:
git config pull.rebase true
That changes my local git configuration *always*, correct?
In the future if I ever try to git push (we have a server setup that everyone pushes to) and someone else has already pushed one or more commits since I last git pulled, I can then git pull and it will *always* rebase my commits?