24
22
Nov 17 '20
No master now, there is. Only main!
Anakin: No!!!!!!!
11
u/toulaboy3 Nov 17 '20
*starts repo first change is to rename main branch to master
6
u/wellickaldersonmoss Nov 17 '20
You can change the default
0
Nov 17 '20
[deleted]
4
u/wellickaldersonmoss Nov 17 '20
I know. I'm saying that it can be changed in GitHub settings. Sorry for not being specific.
1
10
u/CaydendW Nov 17 '20
If you’re like me and very alone, then it’s fine. You don’t have to review your own pull request.
3
14
4
2
u/TheBuckSavage Nov 17 '20
When j was starting out, I just used TortoiseSVN to interact with my repos. About an year later, I was surprised that it even worked at that time.
2
u/g_younes Nov 18 '20
Wait, are we supposed to do something else?
4
u/ThunderChaser Nov 18 '20
If it’s a solo project it’s usually fine.
If you’re working on a larger open source project (or your job) you should almost never push directly to master (and usually you won’t even be allowed to)
3
u/g_younes Nov 18 '20
Oh okay makes sense now. I was half joking half asking - but really that's the first thing I did on github, and I was afraid it might be bad for other reasons. All alone for now so no problems!
2
u/DragoSpiro98 Dec 06 '22
The main problem is conflicts, if it's you alone then no conflicts, because no one else modifies the code, but if you work in team and multiple people are working in different parts, if you push into master, you will have conflicts on each push, if instead you create a branch, work on that and then merge to master, at most you will have a conflict at the end (because you merge only one time)
1
1
u/XungoodkitsuneX Nov 21 '20 edited Nov 21 '20
I can't wait until Jedi Masters are considered offensive, just like master branches are. Because clearly the word master is oppressive. /s
1
-1
-2
97
u/wrtbwtrfasdf Nov 17 '20
"It wouldn't let me push, say's master is protected"
"Use the force"
git push --force