![]() Any links to specific comments you might have will not work anymore. ![]() That -force option will make GitHub accept your push even though the history of the repo they have is unrelated to the empty history that is being pushed.īe aware that this will also close all PRs. That -u flag will automatically set tracking. git commit -m "First commit" # nuke history on GitHub (irreversable) git remote add origin git push -u -force origin master git # create a new local repo git init # add everything git add. Here are the steps I perform: # clone the repo (skip if you already have a cloned repo locally) git clone cd REPOSITORY # remove all history locally rm -rf. Sometimes I don't want people to see all mistakes I've made along the way :-). Min of 4 would be nice.From time to time I need to remove all history from a GitHub repository, for instance right before releasing a package I've worked on in private. 2 Branches might be a bit too little, I think. In my case, I always work with a minimum of 3 branches, the main, the staging/develop and the update(min of 1 but most likely 2). Without the graph, Github Desktop is like a car without a windshield -the engine is powerful and the seats are comfy, but if I can't see where I am and where I'm going, then there's no situation in which I'm going to feel safe driving it anywhere. The reason everyone else includes this is because it's a crucial piece of functionality. Where my current branch is in a project is the most important piece of contextual information I want in repo management. If a project is indeed simple (having only 1 or 2 branches) then this whole point is moot, but for situations where the project graph structure is more complex, then making it impossible to see that complexity is an example of (b). (b) oversimplifying things: making them appear to be simpler than they actually are by hiding relevant and important information that is actually needed. (a) "keeping things simple" (by removing irrelevant or unimportant information), I sincerely hope and the rest of the dev team revisit the idea and start hacking on it. Now that Desktop finally has rollback functionality (YAY to "Create branch from commit") this is the last thing missing for Desktop to become "feature complete" for day-to-day git management - and IMHO the best git GUI available. The advantage of a vertical graph is that you can show the actual commits side-by-side (as in this suggestion) which adds context to the ahead/behind text, making it a valuable addition to the comparison view. But the problem with that design is that it adds no information to the "X commits ahead, Y commits behind" text that Desktop already presents.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |