Reminds me of the time used a private gitlab repo for a freelance contract where I was working alone. I used it to keep track of tasks in issues. Some issues in this repo really turned into me talking to myself
It depends. If you are the owner of a repository with multiple contributors and have rules for code review, then this makes sense. You create the PR so that someone else can say "Yep, meets our standards/tests/release schedule".
But if you start doing stuff like this regularly you probably want to migrate the repository to a dedicated account that exists to own that repository, rather than it be your own.
6 Comments
pcouy@sh.itjust.works · 11 pts · 3y
Reminds me of the time used a private gitlab repo for a freelance contract where I was working alone. I used it to keep track of tasks in issues. Some issues in this repo really turned into me talking to myself
Marxine@lemmy.world · 4 pts · 3y
To be honest it's a good way of tracking your own thought process.
NettoHikari@social.fossware.space · 3 pts · 3y
Are there actual reasons to do this, though?
chillhelm@lemmy.world · 2 pts · 3y
It depends. If you are the owner of a repository with multiple contributors and have rules for code review, then this makes sense. You create the PR so that someone else can say "Yep, meets our standards/tests/release schedule".
But if you start doing stuff like this regularly you probably want to migrate the repository to a dedicated account that exists to own that repository, rather than it be your own.
gkd@lemmy.ml · 2 pts · 3y
Gotta get those GitHub PR numbers up though 💪
FlashPossum@social.fossware.space · 1 pts · 3y
Needs more Jacobs