You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Our team is debating leaving a feature/task branch open vs closing it when we merge that branch into the develop branch through a pull request.
Could we have some input on reasons to keep open vs close?
Couldn't find much information online about this topic and would be good to have some wider opinions.
Thanks
Jake
Thank you!
I'm fairly used to closing feature branches once that work is part of the main branch as I see no reason (yet) to keep it open, it makes sense for any future updates to be made in a new branch from develop.
Looking forward to hearing any more opinions.
Actually the branch management looks cleaner and smarter upon closing a branch after merging to the develop branch
Agreed @Kemboi! Another good reason to opt for closing branches vs leaving them open.