Namely, when describing pagination actions I think it’s probably best to avoid ‘up’ and ‘down’ for naming. Which got me to thinking about naming an pagination conventions.
I’ve been working with some some APIs that have some different patterns for pagination. Simple workflow optimizations like this, make me happy. Here I’ll name them 01-my-fork and 02-origin.īoom! SourceTree picks 01-my-fork by default! Setting your preferred remote as default So, do the ‘ol classic prefixed by numbers. Once we’ve renamed origin, SourceTree will always pick the remote that comes first alphabetically. Open the repo settings (gear in top right)Įditing remote names Changing SourceTree’s Default Remote.Git remote rename origin SproutSocial In SourceTree (I’ve never been a fan of “ origin“, it’s terribly confusing and ambiguous for those learning git). It’s safe to rename the remotes, it’s just a nickname only used locally. Perhaps to the name of owner of the repo like SproutSocial or FaceBook. Since SourceTree always picks origin we just need to rename to anything else. Interestingly all we have to do is rename our remotes. SourceTree defaults pushing new branches to origin Renaming a remote SourceTree defaults to originīy default SourceTree will always pick origin to push a new branch to. Depending on your workflow, you may want to set another remote as your default, let’s say my-fork for instance. When you’re pushing a new branch, SourceTree will automatically guess which remote you wish to push to by default. I’m going to talk about changing SourceTree’s default remote.
0 kommentar(er)
