I've seen projects where they keep feature branches for a long long time. This is something called long-lived branches.
I personally don't like it. I prefer short-lived branches.
In that regard, the only branches I keep in the projects I've worked are the ones related to the flow of deployment:
master
production
Everything else is deleted whenever it's possible: right after merging or when cleaning the repo.
It all depends on what the team wants to do with branches. I've fortunate to always have a say in how to order branches in my teams and this is the way we go.
And also I'm a very organized person and seeing all those branches make me itch and just can't resist the urge to delete them 🤣🤣
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've seen projects where they keep feature branches for a long long time. This is something called long-lived branches.
I personally don't like it. I prefer short-lived branches.
In that regard, the only branches I keep in the projects I've worked are the ones related to the flow of deployment:
Everything else is deleted whenever it's possible: right after merging or when cleaning the repo.
It all depends on what the team wants to do with branches. I've fortunate to always have a say in how to order branches in my teams and this is the way we go.
And also I'm a very organized person and seeing all those branches make me itch and just can't resist the urge to delete them 🤣🤣