|
11 | 11 | * Client
|
12 | 12 |
|
13 | 13 | * Working Directory
|
14 |
| - |
| 14 | + |
15 | 15 | * Trunk
|
16 | 16 |
|
| 17 | + |
| 18 | + |
17 | 19 | ### Basic Functionalities of Source Code Management
|
18 | 20 |
|
19 | 21 | * Add
|
|
50 | 52 |
|
51 | 53 | * Branching and Merging
|
52 | 54 |
|
| 55 | +### CI/CD |
| 56 | + |
| 57 | +In continuous integration practice, a **centralized server** regularly retrieves all new changes to the source code by developers and builds the **software application from scratch.** |
| 58 | + |
| 59 | +The **build and testing of the software is automated and every change or iteration to the software triggers an automated test run to ensure the desired delivery quality.** The central repository is always kept updated in continuous integration practice. |
| 60 | + |
| 61 | +Continuous deployment is the process of building, testing, and releasing the software from the build environment into the production environment automatically without human intervention. Continuous deployment automates the entire testing process and performs more tests on code blocks compared to the usual unit testing done on the code. |
| 62 | + |
53 | 63 | 
|
54 | 64 |
|
55 |
| -### Version Control Systems |
| 65 | +### Version Control System (VCS) |
56 | 66 |
|
57 |
| - |
| 67 | + |
58 | 68 |
|
59 |
| - |
| 69 | + |
60 | 70 |
|
61 | 71 | ### Git
|
62 | 72 |
|
|
70 | 80 |
|
71 | 81 | * As an **efficient version control system**, Git does not store snapshot of files again if nothing has changed in the file and it only stores a link to the previous identical snapshot of the file it has already stored.
|
72 | 82 |
|
73 |
| -#### Three states of a file in Git Project |
74 |
| - |
75 |
| -* Modified |
76 |
| - |
77 |
| -* Staged |
78 |
| - |
79 |
| -* Committed |
80 |
| - |
81 |
| - |
82 |
| - |
83 | 83 | #### Coherence and file tracking using Git VCS
|
84 | 84 |
|
85 | 85 | * Git version control system assigns a checksum to every file or directory before it is stored and the file or directory is referenced by that **checksum**.
|
|
100 | 100 |
|
101 | 101 | 
|
102 | 102 |
|
| 103 | +#### Three states of a file in Git Project |
| 104 | + |
| 105 | +* Modified |
| 106 | + |
| 107 | +* Staged |
| 108 | + |
| 109 | +* Committed |
| 110 | + |
| 111 | + |
| 112 | + |
103 | 113 | #### Features of Git
|
104 | 114 |
|
105 | 115 | * Non-Linear Development Support
|
|
120 | 130 |
|
121 | 131 | * Periodic Packing of files
|
122 | 132 |
|
123 |
| -#### Github API |
124 |
| - |
125 |
| -* There are two stable versions of the GitHub API: the [REST API](https://docs.github.com/en/free-pro-team@latest/rest) and the [GraphQL API](https://docs.github.com/en/free-pro-team@latest/graphql). You can use the **GitHub REST API** to create calls to get the data you need to integrate with GitHub, and the **GitHub GraphQL API** to create precise and flexible queries for the data you need to integrate with GitHub. |
126 |
| - |
127 |
| -* [REST API Guides](https://docs.github.com/en/free-pro-team@latest/rest/guides) help you getting started with the REST API, authentication, and how to use the REST API for a variety of tasks, whenever [GraphQL API Guides](https://docs.github.com/en/free-pro-team@latest/graphql/guides) will help you getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for another variety of tasks. |
128 |
| - |
129 |
| -* It's also possible for [Developers](https://docs.github.com/en/free-pro-team@latest/developers) to go deeper with GitHub by integrating with Github APIs, customizing their GitHub workflow, and building and sharing apps with the community. |
130 |
| - |
131 | 133 | ### GitHub
|
132 | 134 |
|
133 | 135 | 
|
|
0 commit comments