├── .gitignore ├── Configuración_básica_git.md ├── LICENSE ├── README.md ├── Uso_de_SSH_con_Git-GitHub.md └── assets └── img ├── img01.jpg ├── img02.jpg ├── img03.jpg ├── img04.jpg ├── img05.jpg ├── img06.jpg ├── img07.jpg ├── img08.jpg ├── img09.jpg ├── img10.jpg ├── img11.jpg ├── img12.jpg ├── img13.jpg ├── img14.jpg ├── img15.jpg ├── img16.jpg ├── img17.jpg ├── img18.jpg ├── img19.jpg ├── img20.jpg ├── img21.jpg ├── img22.jpg ├── img23.jpg ├── img24.jpg ├── img25.jpg ├── img26.jpg ├── img27.jpg ├── img28.jpg ├── img29.jpg ├── img30.jpg ├── img31.jpg ├── img32.jpg ├── img33.jpg ├── img34.jpg ├── img35.jpg ├── img36.jpg ├── img37.jpg ├── img38.jpg ├── img39.jpg ├── img40.jpg ├── img41.jpg ├── img42.jpg ├── img43.jpg └── img44.jpg /.gitignore: -------------------------------------------------------------------------------- 1 | # Logs 2 | logs 3 | *.log 4 | npm-debug.log* 5 | yarn-debug.log* 6 | yarn-error.log* 7 | lerna-debug.log* 8 | .pnpm-debug.log* 9 | 10 | # Diagnostic reports (https://nodejs.org/api/report.html) 11 | report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json 12 | 13 | # Runtime data 14 | pids 15 | *.pid 16 | *.seed 17 | *.pid.lock 18 | 19 | # Directory for instrumented libs generated by jscoverage/JSCover 20 | lib-cov 21 | 22 | # Coverage directory used by tools like istanbul 23 | coverage 24 | *.lcov 25 | 26 | # nyc test coverage 27 | .nyc_output 28 | 29 | # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files) 30 | .grunt 31 | 32 | # Bower dependency directory (https://bower.io/) 33 | bower_components 34 | 35 | # node-waf configuration 36 | .lock-wscript 37 | 38 | # Compiled binary addons (https://nodejs.org/api/addons.html) 39 | build/Release 40 | 41 | # Dependency directories 42 | node_modules/ 43 | jspm_packages/ 44 | 45 | # Snowpack dependency directory (https://snowpack.dev/) 46 | web_modules/ 47 | 48 | # TypeScript cache 49 | *.tsbuildinfo 50 | 51 | # Optional npm cache directory 52 | .npm 53 | 54 | # Optional eslint cache 55 | .eslintcache 56 | 57 | # Optional stylelint cache 58 | .stylelintcache 59 | 60 | # Microbundle cache 61 | .rpt2_cache/ 62 | .rts2_cache_cjs/ 63 | .rts2_cache_es/ 64 | .rts2_cache_umd/ 65 | 66 | # Optional REPL history 67 | .node_repl_history 68 | 69 | # Output of 'npm pack' 70 | *.tgz 71 | 72 | # Yarn Integrity file 73 | .yarn-integrity 74 | 75 | # dotenv environment variable files 76 | .env 77 | .env.development.local 78 | .env.test.local 79 | .env.production.local 80 | .env.local 81 | 82 | # parcel-bundler cache (https://parceljs.org/) 83 | .cache 84 | .parcel-cache 85 | 86 | # Next.js build output 87 | .next 88 | out 89 | 90 | # Nuxt.js build / generate output 91 | .nuxt 92 | dist 93 | 94 | # Gatsby files 95 | .cache/ 96 | # Comment in the public line in if your project uses Gatsby and not Next.js 97 | # https://nextjs.org/blog/next-9-1#public-directory-support 98 | # public 99 | 100 | # vuepress build output 101 | .vuepress/dist 102 | 103 | # vuepress v2.x temp and cache directory 104 | .temp 105 | .cache 106 | 107 | # Docusaurus cache and generated files 108 | .docusaurus 109 | 110 | # Serverless directories 111 | .serverless/ 112 | 113 | # FuseBox cache 114 | .fusebox/ 115 | 116 | # DynamoDB Local files 117 | .dynamodb/ 118 | 119 | # TernJS port file 120 | .tern-port 121 | 122 | # Stores VSCode versions used for testing VSCode extensions 123 | .vscode-test 124 | 125 | # yarn v2 126 | .yarn/cache 127 | .yarn/unplugged 128 | .yarn/build-state.yml 129 | .yarn/install-state.gz 130 | .pnp.* 131 | -------------------------------------------------------------------------------- /Configuración_básica_git.md: -------------------------------------------------------------------------------- 1 | # Configuraciones Básicas de Git con `git config --global` 2 | 3 | Cuando trabajamos con Git, es importante establecer algunas configuraciones básicas que identificarán al autor de los commits y definirán el comportamiento de Git a nivel global en tu sistema. El comando `git config --global` permite establecer configuraciones que aplican a todos los repositorios de Git en tu sistema. 4 | 5 | ## ¿Por qué usar `git config --global`? 6 | 7 | Configurar tus credenciales y preferencias globalmente asegura que cada vez que realices un commit, la información de autoría esté correctamente asignada. Además, otras configuraciones, como el editor por defecto, pueden mejorar tu flujo de trabajo. 8 | 9 | ## Comandos Esenciales 10 | 11 | ### 1. Configurar tu Nombre de Usuario 12 | Este comando establece el nombre que aparecerá en los commits como autor: 13 | 14 | ```bash 15 | git config --global user.name "Tu Nombre" 16 | ``` 17 | 18 | ### 2. Configurar tu corre eléctrónico 19 | Este comando establece el nombre que aparecerá en los commits como autor: 20 | 21 | ```bash 22 | git config --global user.email "tu.correo@ejemplo.com" 23 | ``` 24 | 25 | ### 3. Configurar el marco de colores 26 | Este comando habilita la visualización de colores en la terminal para los comandos de Git. Esto mejora la legibilidad y facilita la identificación de diferentes tipos de información, como diferencias (`git diff`), estado (`git status`), o ramas (`git branch`), al usar colores específicos: 27 | 28 | ```bash 29 | git config --global color.ui true 30 | ``` 31 | 32 | ### 4. Configurar el Editor por Defecto 33 | Es recomendable configurar el editor de texto por defecto para Git. Esto será útil cuando Git requiera abrir un archivo para que añadas mensajes de commit o resuelvas conflictos: 34 | 35 | ```bash 36 | git config --global core.editor "nano" 37 | ``` 38 | 39 | ### 5. Verificar tus Configuraciones 40 | Para confirmar que tus configuraciones se han aplicado correctamente, puedes ejecutar: 41 | 42 | ```bash 43 | git config --global --list 44 | ``` 45 | 46 | ## ¿Cuándo Usar Estas Configuraciones? 47 | 48 | - Nombre y correo electrónico: Debes configurarlos antes de empezar a trabajar con Git para que tu identidad quede asociada a cada cambio que realices. 49 | - Editor por defecto: Útil cuando Git necesite abrir un editor para mensajes de commit o para resolver conflictos. 50 | 51 | Notas adicionales: 52 | - Si deseas configurar parámetros específicos solo para un proyecto, puedes omitir la bandera --global y Git aplicará las configuraciones solo al repositorio actual. 53 | 54 | 55 | ## ¿Cómo eliminar una configuración global? 56 | 57 | Si deseas eliminar una configuración que previamente has establecido con `git config --global`, el comando a usar es el siguiente: 58 | 59 | ```bash 60 | git config --global --unset 61 | ``` -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 | # Guía Práctica de Git: Domina los Comandos Esenciales 3 | 4 | Esta guía te llevará paso a paso a través de los comandos más importantes de Git, desde la creación de un repositorio local hasta la sincronización con GitHub. Es ideal para desarrolladores que desean fortalecer su flujo de trabajo con Git y asegurar una colaboración eficiente en proyectos de software. 5 | 6 | Este tutorial esta dividido en: 7 | 8 | - **Inicializar un repositorio local** (`git init`) 9 | - **Agregar archivos y realizar commits** (`git add`, `git commit`) 10 | - **Gestionar ramas** (`git branch`) 11 | - **Fusionar ramas** (`git merge`) 12 | - **Conectar con un repositorio remoto** (`git remote`) 13 | - **Subir cambios al repositorio remoto** (`git push`) 14 | - **Verificar el historial de ramas** (`git log --all`) 15 | - **Actualizar el repositorio local desde el remoto** (`git pull`) 16 | - **Resolver conflictos durante la fusión de ramas** 17 | 18 | 19 | Asegurate tener la configuración básica de git y estar autenticado con tu clave SSH: 20 | 21 | - [Configuración básica git](Configuración_básica_git.md) 22 | - [Uso de SSH con Git-GitHub](Uso_de_SSH_con_Git-GitHub.md) 23 | 24 | ## Inicializar un proyecto 25 | 26 | Para realizar los siguientes ejercicios, es necesario tener un archivo o archivos en tu carpeta de trabajo. Si no tienes un proyecto existente, crea un archivo de ejemplo. 27 | 28 | Crea 3 archivos en una carpeta donde comenzarás a generar tu proyecto web. 29 | 30 | ```bash 31 | touch index.html script.js style.css 32 | ``` 33 | 34 |
35 | crear archivos con touch 36 |
37 | 38 | ## Paso 1: Inicializar el repositorio. 39 | 40 | `git init `: Este comando inicializa un nuevo repositorio de Git en el directorio especificado o en el directorio actual si no se especifica uno. 41 | 42 | - ``: El nombre del directorio donde se creará el nuevo repositorio. Si omites este argumento, Git inicializará un repositorio en el directorio actual. 43 | 44 | Este comando crea una carpeta oculta .git que contiene toda la información necesaria para el control de versiones. 45 | 46 | ```bash 47 | git init 48 | ``` 49 | 50 |
51 | git init 52 |
53 | 54 | `git branch -M `: Este comando renombra una rama existente, generalmente utilizada para cambiar el nombre de la rama por defecto. 55 | 56 | - ``: El nombre que quieres asignar a la rama. En este caso, se renombra a "main", que es una convención común actualmente. 57 | 58 | El uso de `-M` fuerza el cambio de nombre, sobrescribiendo cualquier rama existente con el mismo nombre. 59 | 60 | ```bash 61 | git branch -M main 62 | ``` 63 | 64 |
65 | cambiar nombre de rama 66 |
67 | 68 | `git status`: Este comando muestra el estado actual del repositorio de Git, incluyendo: 69 | 70 | - Archivos modificados que aún no se han añadido al área de preparación (staging). 71 | - Archivos que están listos para ser confirmados (committed). 72 | - Archivos no rastreados (untracked) que aún no están bajo control de versiones. 73 | 74 | Es útil para revisar qué cambios se han hecho y qué acciones son necesarias antes de un commit. 75 | 76 | ```bash 77 | git status 78 | ``` 79 | 80 |
81 | saber el estado del repositorio 82 |
83 | 84 | ## Paso 2: Agregar archivos y realizar commits 85 | 86 | `git add `: Este comando añade cambios al área de preparación (staging area) para ser incluidos en el próximo commit. 87 | 88 | - ``: La ruta del archivo o directorio que deseas agregar. Puede ser un archivo específico, varios archivos o usar `.` para agregar todos los cambios en el directorio actual. 89 | 90 | Este comando no realiza un commit, solo prepara los archivos para ser confirmados. 91 | 92 | ```bash 93 | git add . 94 | ``` 95 | ```bash 96 | git status 97 | ``` 98 | 99 |
100 | agregar archivos y directorios 101 |
102 | 103 | `git commit -m ""` : Este comando guarda los cambios preparados en el historial del repositorio junto con un mensaje descriptivo. 104 | 105 | - ``: Es un texto que describe brevemente los cambios realizados en el commit. Debe ser claro y conciso para facilitar el seguimiento del historial de cambios. 106 | 107 | El `-m` permite agregar el mensaje directamente desde la línea de comandos sin abrir el editor de texto. 108 | 109 | ```bash 110 | git commit -m "feat: add empty html, css, and js files" 111 | ``` 112 | 113 |
114 | haciendo commit 115 |
116 | 117 | No existe una convención formal para el mensaje del commit, sin embargo, la [convención de Angular](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) para los commits es ampliamente utilizada porque ofrece beneficios claros en la gestión y mantenimiento de proyectos, y su adopción va más allá de Angular, aplicándose en diversos proyectos open-source y privados: 118 | 119 | ``` 120 | (<área>): 121 | ``` 122 | 123 | - acción: Describe la naturaleza del commit (feat, fix, etc.). 124 | - área: Opcional, describe la parte del proyecto que se está modificando. 125 | - mensaje breve: Describe en pocas palabras qué se está haciendo. 126 | 127 | Acciones comunes de commits: 128 | 129 | - feat: Nueva funcionalidad o característica. 130 | - fix: Corrección de errores. 131 | - chore: Tareas que no afectan el código en sí (por ejemplo, actualizaciones de dependencias). 132 | - docs: Cambios relacionados con la documentación. 133 | - refactor: Modificaciones del código que no corrigen errores ni agregan nuevas funcionalidades. 134 | - style: Cambios que no afectan la lógica del código (formato, espacios, etc.). 135 | - test: Adición o actualización de pruebas. 136 | 137 | GitHub recomienda que los commits sean lo más descriptivos posible, evitando mensajes genéricos como "actualización del código" o "arreglo del código". Esto facilita el rastreo de cambios en el proyecto. 138 | 139 | GitHub fomenta la práctica de commits atómicos, es decir, que cada commit debe hacer una sola cosa (por ejemplo, agregar una función, corregir un error, etc.), lo que facilita la revisión y revertir cambios si es necesario. 140 | 141 | Ejemplos de algunos commmits: 142 | ``` 143 | feat(auth): add JWT authentication for secure login 144 | feat(auth): agregar autenticación JWT para inicio de sesión seguro 145 | 146 | refactor(userService): simplify user validation logic 147 | refactor(userService): simplificar la lógica de validación de usuarios 148 | 149 | style(button): add spaces between buttons 150 | style(button): agregar espacios entre botones 151 | ``` 152 | 153 | `git log`: Este comando muestra información detallada sobre la historia de confirmaciones(`commit`), incluyendo quién realizó cada confirmación, cuándo se hizo y un resumen de los cambios realizados. 154 | 155 | ```bash 156 | git log 157 | ``` 158 | 159 |
160 | mostrar el historial de commits 161 |
162 | 163 | También puedes optar por usar con las sig. opciones: 164 | 165 | - `git log --oneline`: Muestra cada confirmación en una sola línea con su identificador abreviado y el mensaje del commit. 166 | - `git log --graph`: Muestra un gráfico ASCII que representa las relaciones entre las ramas y las confirmaciones. 167 | 168 |
169 | uso de git log --oneline --graph 170 |
171 | 172 | ## Paso 3: Gestionar ramas 173 | 174 | `git branch `: Este comando crea una nueva rama basada en la rama actual. 175 | 176 | - ``: El nombre de la nueva rama que quieres crear. La rama nueva será una copia de la rama actual en el punto en que se encuentra. 177 | Este comando no cambia a la nueva rama automáticamente, solo la crea. 178 | 179 | ```bash 180 | git branch basic-html 181 | ``` 182 | 183 |
184 | uso de git branch 185 |
186 | 187 | `git checkout `: Este comando cambia a la rama especificada y actualiza los archivos en el directorio de trabajo a la última versión confirmada en esa rama. 188 | 189 | - ``: El nombre de la rama a la que quieres cambiar. Si la rama existe, Git cambiará a ella; si no, Git lanzará un error. 190 | 191 | ```bash 192 | git checkout basic-html 193 | ``` 194 | 195 |
196 | uso de git checkout 197 |
198 | 199 | Abre el editor de tu preferencia y escribe la estructura html básica. 200 | 201 | ```html 202 | 203 | 204 | 205 | 206 | 207 | Document 208 | 209 | 210 |

Hello World

211 | 212 | 213 | ``` 214 | 215 |
216 | estructura html básica 217 |
218 | 219 | - Verificando el estado del repositorio 220 | 221 | ```bash 222 | git status 223 | ``` 224 | 225 |
226 | verificar estado del repositorio 227 |
228 | 229 | - `git diff`: Este comando muestra las diferencias entre archivos en el directorio de trabajo y el área de preparación, o entre dos commits. Se puede incluir el nombre de un archivo en específico `git diff filename`. 230 | 231 | ```bash 232 | git diff index.html 233 | ``` 234 | 235 |
236 | diferencias del archivo 237 |
238 | 239 | - `git add .`: agrega la modificación del archivo al área de preparación de Git (staging area). 240 | 241 | ```bash 242 | git add . 243 | ``` 244 | 245 |
246 | prepar archivos 247 |
248 | 249 | - `git commit -m "verbo: mensaje"`: confirma los cambios realizando un `commit`. 250 | 251 | ```bash 252 | git commit -m "feat: basic HTML structure tags" 253 | ``` 254 | 255 |
256 | realizar commit de los cambios 257 |
258 | 259 | - `git status`: información sobre el estado actual del repositorio. 260 | 261 | ```bash 262 | git status 263 | ``` 264 | 265 |
266 | verificar los cambios 267 |
268 | 269 | ## Paso 4: Fusionar ramas. 270 | 271 | Una vez que hayas terminado de desarrollar la funcionalidad en la nueva rama, puedes fusionar los cambios con otra rama, en este caso, la rama `main`. Para realizar la fusión, primero debes cambiar a la rama que recibirá los cambios: 272 | 273 | ```bash 274 | git checkout main 275 | ``` 276 | 277 |
278 | cambiar de rama 279 |
280 | 281 | `git merge `: Este comando combina los cambios de la rama especificada(`basic-html`) en la rama actual(`main`). 282 | 283 | - ``: La rama que quieres fusionar en la rama en la que estás trabajando actualmente. Git integrará los cambios de en tu rama actual. 284 | 285 | Este comando puede generar conflictos si los cambios en ambas ramas afectan las mismas líneas de código; en tal caso, deberás resolver los conflictos manualmente antes de completar el merge. 286 | 287 | ```bash 288 | git merge basic-html 289 | ``` 290 | 291 |
292 | fusionar ramas 293 |
294 | 295 | ```bash 296 | git status 297 | ``` 298 | 299 |
300 | verificar los cambios 301 |
302 | 303 | ## Paso 5: Verificar la conexión remota 304 | 305 | Crea un respositorio nuevo en GitHub. 306 | Se recomienda tener configurada la llave pública para realizar la conexión con la dirección SSH. Si no tienes la configuración revisa la sección [Uso de SSH con Git-GitHub](Uso_de_SSH_con_Git-GitHub.md) 307 | 308 |
309 | crear un reposotorio en github 310 |
311 | 312 | - Copia la direcció SSH del nuevo repositorio. 313 | 314 |
315 | repositorio creado 316 |
317 | 318 | `git remote add `: Este comando agrega una nueva dirección remota a un repositorio Git existente. Puedes hacer la configuración desde cualquier rama. 319 | 320 | - ``: Esto es un nombre descriptivo que le das a la dirección remota. Por convención, "origin" es el nombre más comúnmente utilizado, pero puedes elegir cualquier nombre que tenga sentido para ti. El nombre se utiliza posteriormente para referirse a la dirección remota en otros comandos Git. 321 | 322 | - ``: Aquí debes proporcionar la URL del repositorio remoto al que deseas conectarte. La URL puede ser una dirección HTTP/HTTPS o una dirección SSH, dependiendo de cómo esté configurado el repositorio remoto. 323 | 324 | ```bash 325 | git remote add origin git@github.com:usergithub/cohorte-x-sesions.git 326 | ``` 327 | 328 |
329 | agregar repositorio remoto 330 |
331 | 332 | - `git remote`: Se utiliza en Git para mostrar una lista de las direcciones remotas (remotes) configuradas en un repositorio Git junto con sus URL asociadas. 333 | - `git remote -v`: La opción -v o --verbose muestra información detallada sobre cada una de las direcciones remotas. 334 | 335 | ```bash 336 | git remote -v 337 | ``` 338 | 339 |
340 | mostrar los repositorios remotos configurados 341 |
342 | 343 | ## Paso 5: Subir cambios al repositorio remoto 344 | 345 | `git push origin main`: Este comando se utiliza en Git para enviar (subir) tus cambios locales en la rama `main` de tu repositorio local al repositorio remoto (GitHub) denominado "origin". 346 | 347 | - `origin`: El nombre del repositorio remoto. Por convención, `origin` es el nombre predeterminado para el repositorio remoto original, pero puedes tener otros remotos con diferentes nombres. 348 | - `main`: La rama local que deseas enviar al remoto. 349 | 350 | ```bash 351 | git push origin main 352 | ``` 353 | 354 |
355 | subir cambios al repositorio remoto 356 |
357 | 358 | - Si deseas subir otra rama tendrás que idicarla `git push origin basic-html`. 359 | 360 | Verificar los cambios en GitHub en la rama main. 361 | 362 |
363 | subir cambios al repositorio remoto 364 |
365 | 366 | - Puedes trabajar en otra rama y hacer merge a tu rama main, posteriormente hacer de nueva `git push origin main`. Puedes hacer varios `commits` y al final un solo `git push`. 367 | 368 | ## Paso 7: Verificar el historial de ramas 369 | 370 | `git log --oneline --graph --all`: Obtendrás una vista gráfica de la historia de confirmaciones de tu repositorio que incluye todas las ramas. Esto te permite ver de un vistazo cómo se desarrolla el proyecto, dónde se realizan fusiones y bifurcaciones, y cuáles son las confirmaciones más recientes. 371 | 372 | ```bash 373 | git log --oneline --graph --all 374 | ``` 375 | 376 | - En Git, la rama que contiene la referencia especial `HEAD` indica la rama actual en la que te encuentras trabajando. `HEAD` es un puntero que apunta al último commit de la rama actual, y por lo tanto, representa la posición actual en la historia de confirmaciones del repositorio. 377 | 378 |
379 | subir cambios al repositorio remoto 380 |
381 | 382 | La imagen anterior nos muestra que tienes dos ramas locales: `main` y `basic-html` que están al mismo nivel de historia, es decir, están sincronizadas en el commit 093a21a. 383 | 384 | Por otro lado, `origin/main` indica una rama remota llamada `main` en el repositorio remoto que está configurado como `origin`. La rama `origin/main` rastrea la versión de `main` en el repositorio remoto. Puedes sincronizar tus cambios locales con esta rama remota mediante comandos como `git push` o `git pull`. 385 | 386 | ## Paso 8: Actualizar el repositorio local desde el remoto 387 | 388 | En GitHub abre el archivo index.html dandole clic. 389 | 390 |
391 | repositorio en github 392 |
393 | 394 | - Pulsa el ícono de lapiz para editar el documento y agrega nueva información. 395 |
396 | editar archivo 397 |
398 | 399 | - Pulsa el botón `Commit changes...` para realizar un commit. Se recomienda seguir con el mismo formato que estés usando en tus commits locales. Para finalizar pulsa el botón `Commit changes`. 400 | 401 |
402 | editar archivo 403 |
404 | 405 | Regresa a tu repositorio local y situate en la rama `main`, utiliza `git log --oneline --graph --all` para obtener una vista gráfica de la historia de confirmaciones de tu repositorio. 406 | 407 | ```bash 408 | git log --oneline --graph --all 409 | ``` 410 | 411 |
412 | verificar el estado de mis ramas 413 |
414 | 415 | `git fetch origin main`: Este comando se utiliza en Git para recuperar los cambios de la rama main del repositorio remoto llamado `origin`` sin fusionar automáticamente estos cambios con tu rama local. 416 | 417 | - `origin`: El nombre del repositorio remoto del que estás obteniendo los cambios. 418 | - `main`: La rama en el repositorio remoto que deseas descargar. 419 | 420 | `git fetch` solo actualiza tu repositorio local con los datos del remoto, sin modificar tu rama actual. Para integrar esos cambios, debes usar `git merge` o `git rebase`. 421 | 422 | ```bash 423 | git fetch origin main 424 | ``` 425 | 426 |
427 | uso de git fetch 428 |
429 | 430 | - Puedes verificar con `git log --oneline --graph --all` el estado de las ramas locales y remotas. En la siguiete imagen se muestra que la rama remota `origin/main` tiene un commit (ae1a138) más en la historia que la rama local `main` (093a21a). 431 | 432 | ```bash 433 | git log --oneline --graph --all 434 | ``` 435 | 436 |
437 | uso de git log --oneline --graph --all 438 |
439 | 440 | `git merge origin/main`: Este comando fusiona los cambios de la rama main del repositorio remoto origin en tu rama local actual. 441 | 442 | - `origin/main`: La referencia a la rama main en el repositorio remoto origin. 443 | 444 | Este comando integra los cambios descargados de `origin/main` en tu rama local actual, actualizando tu rama con los últimos cambios del repositorio remoto. Si hay conflictos, tendrás que resolverlos antes de completar el merge. 445 | 446 | ```bash 447 | git merge origin/main 448 | ``` 449 | 450 |
451 | uso de git merge origin/main 452 |
453 | 454 | - Puedes verificar con `git log --oneline --graph --all` el estado de las ramas locales y remotas. 455 | 456 |
457 | uso de git log --oneline --graph --all 458 |
459 | 460 | Una alternativa de `git fetch` y `git merge` es usar `git pull `: Este comando se utiliza en Git para recuperar (fetch) los cambios de la rama main del repositorio remoto llamado `origin` y fusionar (merge) automáticamente esos cambios con tu rama local. 461 | 462 | ```bash 463 | git pull origin main 464 | ``` 465 | 466 | ## Resolver conflictos durante la fusión de ramas 467 | 468 | Si otros colaboradores han realizado cambios en el repositorio remoto en las mismas líneas de código que tú has modificado localmente, podrías enfrentar conflictos de fusión. Al hacer un git pull, tendrás la oportunidad de resolver los conflictos de manera proactiva antes de enviar tus cambios. Esto facilita la gestión de conflictos, ya que puedes resolverlos localmente antes de confirmar tus cambios. 469 | 470 | En el siguiente ejercicio se modificará la misma línea en el archivo index.html localmente y en GitHub, posteriomente en tu repositorio local se realizará `git pull` por lo que git indicará que hay un conflicto en el archivo. 471 | 472 | Modificar localmente el archivo index.html cambiando el contenido de la etiqueta h1 a "Generation Mx". Guarda los cambios. 473 | 474 |
475 | confirmando los cambios en index.html 476 |
477 | 478 | - Agrega las modificaciones al área de preparación con `git add .` y confirma los cambios con `git commit`. 479 | 480 | Modifica el archivo index.html desde GitHub cambiando el contenido de la etiqueta h1 a "HTML, JS, CS". 481 | 482 |
483 | modificando index.html 484 |
485 |
486 | confirmando los cambios en index.html 487 |
488 | 489 | `git pull `: Este comando se utiliza en Git para recuperar (fetch) los cambios de la rama main del repositorio remoto llamado `origin` y fusionar (merge) automáticamente esos cambios con tu rama local. 490 | 491 | ```bash 492 | git pull origin main 493 | ``` 494 | 495 |
496 | git pull origin main 497 |
498 | 499 | Cuando en Git ves que una rama aparece con el formato `main|MARGIN`, eso generalmente significa que la rama en la que te encuentras (en este caso, "main") tiene cambios pendientes (commits) que aún no se han enviado (push) al repositorio remoto. 500 | 501 | - Puedes ejecutar `git status` para conocer el estado de tu repositorio. El mensaje "You have unmerged paths" en Git significa que tienes conflictos de fusión sin resolver en tu repositorio. Esto ocurre cuando Git no puede fusionar automáticamente dos ramas debido a cambios conflictivos en el mismo archivo o línea de código. 502 | 503 | ```bash 504 | git status 505 | ``` 506 | 507 |
508 | estado del repositorio 509 |
510 | 511 | Abre el archivo `index.html` y se mostrará 512 | 513 | ```html 514 | <<<<<< HEAD 515 | cambios locales 516 | ======== 517 | cambios remotos 518 | >>>>> HASH de Commit 519 | ``` 520 | 521 |
522 | conflictos en index.html 523 |
524 | 525 | - Realiza las modificaciones adecuadas eliminado, uniendo o agregando elementos, esto lo puedes realizar manualmente, no olvides quitar los decoradores `<<< === >>> `. Algunos IDEs te ayudan a realizar el cambio pulsando las opciones "Accept Current Changes", "Accept Incoming Cahnge", "Accept Both Changes". 526 | 527 |
528 | conflictos resueltos 529 |
530 | 531 | Agrega y confirma tus cambios con `git add .` y `git commit -m `. 532 | 533 |
534 | git add y git commit 535 |
536 | 537 | Sube tus cambios locales a tu repositorio remoto con `git push`. 538 | 539 |
540 | git push 541 |
542 | 543 | Se recomienda hacer `git pull` antes de `git push`. Esto asegura que tu rama local esté actualizada con los últimos cambios del repositorio remoto antes de subir tus propios cambios. Al hacer `git pull`, Git descarga y fusiona los cambios remotos en tu rama local, lo que ayuda a evitar conflictos y asegura que tu historial de commits esté alineado con el repositorio remoto. -------------------------------------------------------------------------------- /Uso_de_SSH_con_Git-GitHub.md: -------------------------------------------------------------------------------- 1 | # Uso de SSH con Git y GitHub 2 | 3 | Cuando trabajas con GitHub, existen dos formas principales de autenticarte al clonar, hacer push o pull en repositorios: **HTTPS** y **SSH**. 4 | 5 | Con el protocolo SSH, puedes conectarte y autenticarte a servidores y servicios remotos. Con las claves SSH, puedes conectarte a GitHub sin tener que proporcionar tu nombre de usuario y token de acceso personal en cada visita. 6 | 7 | A continuación se detallan las ventajas y desventajas de cada método para ayudarte a decidir cuál usar según tu caso. 8 | 9 | ## Ventajas y Desventajas de usar HTTPS vs SSH en GitHub 10 | 11 | | Característica | HTTPS | SSH | 12 | |--------------------|-----------------------------------------|---------------------------------------| 13 | | **Facilidad de uso** | Alta, sin configuración inicial | Media, requiere configuración inicial | 14 | | **Seguridad** | Media (segura con tokens) | Alta (autenticación por clave) | 15 | | **Autenticación** | Contraseña/token por cada operación | Automática con la llave SSH | 16 | | **Acceso desde múltiples máquinas** | Fácil (solo contraseña o token) | Requiere configuración en cada máquina | 17 | | **Restricciones de red** | Menos probable que esté bloqueado | Puede ser bloqueado por firewalls | 18 | 19 | ### ¿Cuál elegir? 20 | 21 | - **Elige HTTPS** si prefieres una configuración rápida, trabajas en múltiples máquinas o entornos donde es más fácil administrar contraseñas o tokens. 22 | - **Elige SSH** si buscas mayor seguridad y comodidad a largo plazo, especialmente si trabajas en una sola máquina o tienes facilidad para configurar SSH en varias máquinas. 23 | 24 | ## Generar una nueva llave SSH y registrarla en GitHub 25 | 26 | ### 1. Generar una nueva llave SSH 27 | Si no tienes una llave SSH o prefieres generar una nueva, usa el siguiente comando: 28 | 29 | ```bash 30 | ssh-keygen -t ed25519 -C "tu.correo@ejemplo.com" 31 | ``` 32 | 33 | - -t ed25519: Especifica el tipo de encriptación. ed25519 es más moderna y segura. Si tu sistema no lo soporta, puedes usar rsa con -t rsa. 34 | - -C: Es un comentario que suele ser tu correo electrónico para identificar la llave. 35 | 36 | Nota: Si está utilizando un sistema que no admite el algoritmo Ed25519, utilice: 37 | 38 | ```bash 39 | ssh-keygen -t rsa -b 4096 -C "tu.correo@ejemplo.com" 40 | ``` 41 | 42 | ### 2. Copiar tu clave pública 43 | Para usar la autenticación SSH en GitHub, necesitas copiar la clave pública y añadirla a tu cuenta de GitHub. Usa el siguiente comando para copiarla al portapapeles: 44 | 45 | ```bash 46 | cat ~/.ssh/id_ed25519.pub 47 | ``` 48 | 49 | Copia el contenido que aparece en pantalla. 50 | 51 | ### 3. Añadir tu clave SSH en GitHub 52 | 53 | 1. Accede a GitHub y ve a Ajustes de SSH. 54 | 2. Haz clic en "New SSH Key". 55 | 2. Pega tu clave pública copiada en el campo "Key". 56 | 4. Da un nombre a la llave en el campo Title (puedes usar el nombre de tu máquina para identificarla). 57 | 5. Haz clic en "Add SSH Key". 58 | 59 | ### 4. Verificar la conexión SSH con GitHub 60 | Para asegurarte de que la llave SSH está correctamente configurada y funciona, prueba la conexión con el siguiente comando: 61 | 62 | ```bash 63 | ssh -T git@github.com 64 | ``` 65 | 66 | Si todo está correcto, recibirás un mensaje similar a: 67 | 68 | "Hi username! You've successfully authenticated, but GitHub does not provide shell access." -------------------------------------------------------------------------------- /assets/img/img01.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img01.jpg -------------------------------------------------------------------------------- /assets/img/img02.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img02.jpg -------------------------------------------------------------------------------- /assets/img/img03.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img03.jpg -------------------------------------------------------------------------------- /assets/img/img04.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img04.jpg -------------------------------------------------------------------------------- /assets/img/img05.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img05.jpg -------------------------------------------------------------------------------- /assets/img/img06.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img06.jpg -------------------------------------------------------------------------------- /assets/img/img07.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img07.jpg -------------------------------------------------------------------------------- /assets/img/img08.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img08.jpg -------------------------------------------------------------------------------- /assets/img/img09.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img09.jpg -------------------------------------------------------------------------------- /assets/img/img10.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img10.jpg -------------------------------------------------------------------------------- /assets/img/img11.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img11.jpg -------------------------------------------------------------------------------- /assets/img/img12.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img12.jpg -------------------------------------------------------------------------------- /assets/img/img13.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img13.jpg -------------------------------------------------------------------------------- /assets/img/img14.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img14.jpg -------------------------------------------------------------------------------- /assets/img/img15.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img15.jpg -------------------------------------------------------------------------------- /assets/img/img16.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img16.jpg -------------------------------------------------------------------------------- /assets/img/img17.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img17.jpg -------------------------------------------------------------------------------- /assets/img/img18.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img18.jpg -------------------------------------------------------------------------------- /assets/img/img19.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img19.jpg -------------------------------------------------------------------------------- /assets/img/img20.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img20.jpg -------------------------------------------------------------------------------- /assets/img/img21.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img21.jpg -------------------------------------------------------------------------------- /assets/img/img22.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img22.jpg -------------------------------------------------------------------------------- /assets/img/img23.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img23.jpg -------------------------------------------------------------------------------- /assets/img/img24.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img24.jpg -------------------------------------------------------------------------------- /assets/img/img25.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img25.jpg -------------------------------------------------------------------------------- /assets/img/img26.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img26.jpg -------------------------------------------------------------------------------- /assets/img/img27.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img27.jpg -------------------------------------------------------------------------------- /assets/img/img28.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img28.jpg -------------------------------------------------------------------------------- /assets/img/img29.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img29.jpg -------------------------------------------------------------------------------- /assets/img/img30.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img30.jpg -------------------------------------------------------------------------------- /assets/img/img31.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img31.jpg -------------------------------------------------------------------------------- /assets/img/img32.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img32.jpg -------------------------------------------------------------------------------- /assets/img/img33.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img33.jpg -------------------------------------------------------------------------------- /assets/img/img34.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img34.jpg -------------------------------------------------------------------------------- /assets/img/img35.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img35.jpg -------------------------------------------------------------------------------- /assets/img/img36.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img36.jpg -------------------------------------------------------------------------------- /assets/img/img37.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img37.jpg -------------------------------------------------------------------------------- /assets/img/img38.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img38.jpg -------------------------------------------------------------------------------- /assets/img/img39.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img39.jpg -------------------------------------------------------------------------------- /assets/img/img40.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img40.jpg -------------------------------------------------------------------------------- /assets/img/img41.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img41.jpg -------------------------------------------------------------------------------- /assets/img/img42.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img42.jpg -------------------------------------------------------------------------------- /assets/img/img43.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img43.jpg -------------------------------------------------------------------------------- /assets/img/img44.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sergiotrrs/git-basic-commands/34052926eba2037a823091838e95cfefa10d1e07/assets/img/img44.jpg --------------------------------------------------------------------------------