Showing results for 
Search instead for 
Did you mean: 
Copilot Lvl 2
Message 1 of 2

Fully Commit and "Complete" Branch and work.

I'm not new to the concept of version repositories but am slightly confused with the logic behind branches.


I understand that the way to push changes from a branch to the master is through a pull request. So once done with a change what I'd like to do is to complete the pull request and put the branch in a sort of closed state. Unfortunately I don't seem to be able to close a branch through github short of deleting it which doesn't seem like the ideal way to do things. I do want to make the branch so that it no longer can be worked under, effectively acting as a record of that branches existance. In the circumstance that I needed to later fix something that the original branch was intending to build / fix I figure I'd just create a new branch at that point and do all necessary changes under the new branch. 


Is this standard for this version repository or am I misunderstanding a critical design choice associted with Github that might warrent trying to do things a different way?


Thanks in advance.

1 Reply
Community Manager
Message 2 of 2

Re: Fully Commit and "Complete" Branch and work.

Hi @misterbee180,


Thanks for being here! Branching is an essential part of your Git workflow, deleting your branch post-merge is known as best practice. To learn more about branches check out the docs


Perhaps another user will chime in with their understanding of branching but I hope this helps!

Thanks for being here, sharing, and keeping our community awesome!

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!