-
Notifications
You must be signed in to change notification settings - Fork 3
Halil Umut Özdemir Git Research
Version control software keeps track of every modification to the code in a special kind of database. If a mistake is made, code can be turned back to the earlier versions.
Version control software helps prevent concurrent work from conflicting. So, 2 different developers can make changes to different parts of the same code.
Branching and merging is also a benefit of Git. With branches, Git can keep multiple streams of work independent from each other while also providing the feature to merge them. So, for any software different branches can be created for the development part and in the end, all branches can be merged.
Distributed version control systems are one of the categories of the version control systems. In distributed models, there is no central computer and every developer has a complete copy of the project.
Git is a free and open-source Distributed Version Control System.
-
Commit: For the perspective of Git, data is a set of snapshots. For every commit or save, Git takes a snapshot of the project to keep track of every modification.
-
Repository: A directory that contains the project and some files to communicate with Git.
-
Staging Area: A file that stores the information about the changes of your directory. These changes will be the information needed in the next commit.
A Git repository can be viewed as 3 main areas: the working directory, the staging area, and the repository that the commits will be saved.
To make any change in the repository, the first files that have modification must be added to the Staging Area. For each commit, Git stores a snapshot of files with modifications and gives each commit a 7 digit id. Also, each commit has a commit message, it is important to create meaningful messages for each commit.
We can add some tags to our commits. With using these tags the important commits can be remembered. For example, at the end of the development of each version of the software, a tag can be added to remember to the last commit.
Branches can be thought of as a series of commits and some pointers that point the latest commit in that series. When a new branch is created, a new pointer is initialized at your current branch. If you make any commit to the new branch the old branch is not affected by this commit.
Merging is combining two branches. To merge 2 branches Git creates a new commit and combines 2 branches on that new commit. While merge operation there can be some conflicts. To merge 2 branches all conflicts must be solved. There are some merge conflict indicators that is explained in the link
When we want to take the commits in the remote repository to our local repository, we make a pull. When we send the commits made in our local repository to the remote repository, we make a push.
- Requirements
- Workspace Creation Scenario
- Application to a Workspace Scenario
- Follow Mechanism Scenario
- Design Documents
- Plan Documents
- Milestone Reports
- API Documentation
- Manuals
- Burak Ömür
- Halil Umut Özdemir
- Hasan Ramazan Yurt
- Öykü Yılmaz (Communicator)
- Ahmet Dadak
- Ertuğrul Bülbül
- Alperen Divriklioğlu
- Burhan Can Akkuş
- Hüseyin Can Bölükbaş
- Hilal Demir
- Umutcan Uvut
- Orkan Akisu
- Frontend Meeting #7 (19.01.2021)
- Frontend Meeting #6 (12.01.2021)
- Android Meeting #5 (08.01.2021)
- Frontend Meeting #5 (05.01.2021)
- Backend Meeting #6 (30.12.2020)
- Meeting #26 (29.12.2020)
- Meeting #25 (28.12.2020)
- Backend Meeting #5 (23.12.2020)
- Frontend Meeting #4 (21.12.2020)
- Android Meeting #4 (18.12.2020)
- Backend Meeting #4 (16.12.2020)
- Meeting #24 (15.12.2020)
- Meeting #23 (09.12.2020)
- Frontend Meeting #3 (10.12.2020)
- Android Meeting #3 (09.12.2020)
- Backend Meeting #3 (09.12.2020)
- Frontend Meeting #2 (08.12.2020)
- Android Meeting #2 (07.12.2020)
- Frontend Meeting #1 (03.12.2020)
- Android Meeting #1 (02.12.2020)
- Backend Meeting #2 (02.12.2020)
- Meeting #22 (25.11.2020)
- Meeting #21 (21.11.2020)
- Backend Meeting #1 (18.11.2020)
- Meeting #20 (17.11.2020)
- Meeting #19 (10.11.2020)
- Meeting #18 (30.10.2020)
- Meeting #17 (27.10.2020)
- Meeting #16 (24.05.2020)
- Meeting #15 (13.05.2020)
- Meeting #14 (10.05.2020)
- Meeting #13 (07.05.2020)
- Meeting #12 (30.04.2020)
- Meeting #11 (23.04.2020)
- Meeting #10 (17.04.2020)
- Meeting #9 (16.04.2020)
- Meeting #8 (09.04.2020)
- Meeting #7 (22.03.2020)
- Meeting #6 (12.03.2020)
- Meeting #5 (05.03.2020)
- Meeting #4 (28.02.2020)
- Customer Meeting #1 (28.02.2020)
- Meeting #3 (27.02.2020)
- Meeting #2 (20.02.2020)
- Meeting #1 (13.02.2020)
- Meeting Notes Template