Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,557,117
Community Members
 
Community Events
184
Community Groups

Pull request into develop branch - should you close feature branch on merge?

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

1 comment

Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 20, 2020

Hi @Jake Walters,

Welcome to the Community!

I'm going to start by saying that I'm sure there are really good reasons for either option, it depends on how you work.

We opt to close branches as soon as a feature has merged.  Why? Because it takes seconds to recreate them if you really need something with the same name.  However, if we leave them open we need to constantly refresh with a merge from the development branch to keep the branch in sync.

That's my two cents.  I'd love to hear the thoughts and opinions from others.

-Jimmy

Like # people like this

Hi @Jimmy Seddon 

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.

Like # people like this

Hi @Jimmy Seddon  

Actually the branch management looks cleaner and smarter upon closing a branch after merging to the develop branch

Like # people like this
Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 02, 2020

Agreed @Kemboi!  Another good reason to opt for closing branches vs leaving them open.

Like # people like this

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events