Skip to content
loading...

re: Hack or maybe not: "Deleting" master when it gets too big VIEW POST

FULL DISCUSSION
 

Ohhhhhhhhhhhhhhhhh, no, please don't. master should be your canonical "we checked that this code works". If deleting master seems like a "good idea," the team workflow is seriously borked, and you need to get outside help to overhaul it.

 

Thanks for giving me perspective. I always enjoy these threads cause I'm never 100% sure of the approach but my lack of experience makes me real malleable

 

The author did not actually delete master on the remote repo, if that's what you're implying.

 

While I wasn't entirely certain which master he referred to, my concern stands in either case. See my replies to the other comment pointing out that he meant "delete local master".

 

If deleting master seems like a "good idea," the team workflow is seriously borked [...].

Like how?

code of conduct - report abuse