In a later step, I have sent information to the developers, how they can use the tag to retain their branch. For that, I have written a little script that helps to replace branches by tags. However, I wanted to give everybody the possibility to re-create the branch in question. On one hand, cleaning the repo from binaries was a good opportunity to substantially reduce the number of branches. Step 3 (optional): Replace remote Branches by Tags Step 2: Move and Fork the RepoĪs a kind of backup of the repo, I recommend to move the repository and work on a forked copy of the repo. I recommend that you disallow any changes to the repo apart the one you are performing. Repos like BitBucket allow fine-grained control over who is allowed to do what. The changes are destructive, and even if you fork the repository, there is no easy way to revert all the changes. In our case, the GIT history has grown to 223 MB, because a binary of ~40 MB was updated several times: du -h -d 1įirst of all, you need to inform everybody, what you are going to do, and when it will be done. See this GIT repo, which will promote a simple example how BFG can be used. However, I have tested BFG privately in this GIT Repo and I can recommend its usage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |