Pull Request branch deletion

[theduyngx]

Hey all, I've been wanting to have a discussion a bit about what to do with a topic-specific branch after the Pull Request created for it is approved for merge.

The idea of a topic-specific PR (branch with no protection rule, and is only specific to a single topic) is that, if it's incomplete for merge, it should not yet be merged and the PR will continue to be Open until it is ready to be approved for merge. Once it is merged, it seems that the convention is to delete the branch to clean up the Repository list of branches.

For more information, you can read here and here.

Ultimately, this is only so that the repository is not cluttered with stale branches. And if you are currently developing on an already deleted branch, you can always move uncommitted changes to a new branch via running git checkout -b new-branch. So it should be quite safe either way I believe.

I'd like to hear your thoughts on this, and whether you like it or would prefer not to have it. @Lyonville/team7 @Lyonville/weexcel @Lyonville/damolab @Lyonville/iwanth1 @Lyonville/hillclimbers.

[konfucius1]

Yep. generally for housekeeping, a branch is no longer needed after it's been merged.

[jonathancjk]

Yeah, I think that deleting the branch after it's merged makes sense. Helps to keep the repo tidier like what Duy and Thanakon said.

[theduyngx]

I'll keep this discussion open till end of the project. Although if no one has any further thoughts on this, we will probably start doing this as soon as next week. Thanks everyone!