developer account set up
hi-angel at yandex.ru
Tue May 9 15:25:26 BST 2023
On Tue, 2023-05-09 at 10:57 +0200, Johnny Jazeix wrote:
> > I remember when we were integrating Gitlab at work, people for some reason
> > were
> > attempting to create branches in the upstream repo rather than on their own
> > fork. Had to do some explanation that this isn't the way to go, because
> > after an
> > year of such workflow upstream will end up with hundreds if not thousands of
> > abandoned branches that serve no purpose, and who's gonna clean that up
> > 🤷♂️
> > Especially given that people may come and go, and so in some cases you
> > wouldn't
> > even find an author of a branch (and in some cases it's hard to even figure
> > out
> > who could be the author in the first place).
> The issues you mentioned are the same with forks. Instead of having abandoned
> branches in the main repo where maintainers could know if they are active or
> not, we will have abandoned branches in abandoned repositories without MR to
> know they exist and they would need to be cleaned.
A fork belongs to a user account though. That knowledge simplifies cleaning
process as for example one could send to the user a notification saying that
their fork has not seen any activity in months and asking if it's still needed.
And then in absence of answer for some determined amount of time to delete the
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kde-devel