Good Practices.... 1. Obviously read a few good books or article. Such as https://git-scm.com/book/en/v2 2. Try to understand the background and philosophy, especially the 'distributedness'. 3. Each user has full local control. They should make best use of that. (that includes you;-) 4. Create branches, and commits early and often, usually starting from origin/master, so you are already working with the best upstream code. 5. Branching is easy, see 4. 6. don't worry about mistakes (see 3). your data is secured as long as you 'added' it to the repository, or even better committed it. 7. write nice commit messages. The small effort in writing concise messages will be beneficial (always say what/why to did the changes)
10. Look up 'interactive rebasing' where you tidy up your mistakes and polish your code (see 6). 11. look up "PushRemote" (where you store stuff), to distinguish your code from 'Upstream' the place where you get the latest authorised code. On Monday, May 4, 2020 at 4:18:40 PM UTC+1, Kunal Chauhan wrote: > > I am new to git so can you elaborate what are the good practices. > > On 4 May 2020 4:40 p.m., "Philip Oakley" <philipoakley l> wrote: > > Hi Kunal > > > On Monday, May 4, 2020 at 11:10:44 AM UTC+1, Kunal Chauhan wrote: >> >> Hi Team, >> >> 1. I want to check all the changed file in git with date time and some >> color coding that can help be to check easily >> > > Lots of options and possibilities.Hopefully you are already using good > practice of lots of small changes for easy review and testing. This means > that deciding where to look in the sequence of commits becomes a proper > choice. > > You can use `git blame` to show who changed which line on which commit. > You can limit the blame to a small range of commits, or commits `since` a > time point, and use `-b` to not show the older commits for unchanged lines. > > You can use `git diff` to see the totality of changes between two commits, > either start-end or intermediate point to other point. It usually has > colour (if enabled). `Git show` will list all the commits and their diffs - > use the range and `since` options to avoid overload. > > > >> 2. I want to check the my branch where it has been created and logs on ti >> > > `Git log` with the 'two dot' range will show everything on one branch, > since it was forked from another e.g. `master..mybranch` > > Also have a look at gitk to visualise the branch structure. (other tools > are available) > > > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/git-users/89fff836-d070-4ebc-a418-5c0dc3e4af67%40googlegroups.com > > <https://groups.google.com/d/msgid/git-users/89fff836-d070-4ebc-a418-5c0dc3e4af67%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/3d77201a-4a9b-4064-be5c-20ea0d17db7d%40googlegroups.com.
