Information on a repository's commits page.įor more information on how Git considers commit history, see the "History Simplification" section of the git log help article. If you want to see the entire history, GitHub provides a view with more This truncated view might not always contain the information you'reĪfter. This makes reviewing branches more efficient, since you only see the commits that affect the file. For example, if a side branch made a change and then reverted it, that commit would not show up in the branch history. I know why they want the data, and Im alright with it. It makes the history simpler by removing commits that didn't contribute to the final result. The Significant Locations list shows a minute-by-minute route history of my. Any commits on theīranch that touched the file will not be shown.įor a file's commit history, GitHub explicitly follows this simple strategy. When merged, did not impact the final contents of the file. Instead of looking at every commit toĭecide whether it touched the file, Git will omit a whole branch if that branch, ![]() When Git shows the history of a single file, it simplifies history by omittingĬommits that did not change the file. Git has several different ways of showing the history of a repository. The history for a single file may omit commits found on the repository's commit history. These two commit views may show different information at times.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |