Changes between Version 12 and Version 13 of Csle2022/Agenda/scriptingandgithub


Ignore:
Timestamp:
Nov 3, 2022, 4:38:00 AM (19 months ago)
Author:
deepthi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Csle2022/Agenda/scriptingandgithub

    v12 v13  
    209209Here, * represent represents minute(s) hour(s) day(s) month(s) weekday(s), respectively.
    210210
    211 = Github administration =
    212 
    213 === Install Git and create a Github account ===
    214 
    215 To see if you already have Git installed, open up your terminal application.
    216 
    217 Once you've opened your terminal application, type git version. The output will either tell you which version of Git is installed, or it will alert you that git is an unknown command. If it's an unknown command, read further and find out how to install Git.
    218 
    219 Install git:
    220 
    221 Debian/Ubuntu
    222 
    223 Git packages are available using `apt`.
    224 
    225 It's a good idea to make sure you're running the latest version. To do so, Navigate to your command prompt shell and run the following command to make sure everything is up-to-date: `sudo apt-get update`.
    226 
    227 To install Git, run the following command: `sudo apt-get install git-all`.
    228 
    229 Once the command output has completed, you can verify the installation by typing: `git version`.
    230 
    231 To create the github account:
    232 
    233 Navigate [https://github.com] and signup with your details
    234 
    235 === Install source tree on your computer ===
    236 
    237 === Create a local Git repo ===
    238 
    239 ===== Every git repository has three trees. A working directory, Index and Head. ====
    240 
    241 - Working directory: It contains the actual project files.
    242 
    243 - Index: It is the staging area where you add the project files that needs to be committed.
    244 
    245 - Head: Head is where the reference to you previous commit exists.
    246 
    247 git init is one way to start a new project with Git. To start a repository, use either `git init` or `git clone` - not both.
    248 
    249  To initialize a repository, Git creates a hidden directory called `.git`. That directory stores all of the objects and refs that Git uses and creates as a part of the project's history. This hidden `.git` directory is what separates a regular directory from a Git repository.
    250 
    251 {{{
    252 git init: One Person Starting a New Repository Locally
    253 git clone: The Remote Already Exists
    254 }}}
    255 
    256 === Add a new file to the repo ===
    257 === Add a file to the staging environment ===
    258 
    259 === Create a commit ===
    260 === Create a branch ===
    261 === Create a new repo on Github ===
    262 === Push a branch to GitHub ===
    263 === Create a pull request ===
    264 === Merge a pull request ===
    265 ===  Get changes on your Github back your computer ===
    266 
    267 ==== Committing new changes to the repository (commit): ====
    268 
    269 Once you have added all the files to the staging area, you can commit the changes with a reference message using the “-m” flag as shown below.
    270 
    271 git commit -m “my first commit”
    272 
    273 
    274 
    275 
    276 
    277 
    278 ==== Checking out a repository ====
    279 
    280 You can create a copy of your git repository using the clone command. Execute the following command to clone your project directory.
    281 
    282 `git clone /path/to/project-repository`
    283 
    284 
    285 
    286 ==== Adding file to the staging area: (add) ====
    287 
    288 `git add <filename>`
    289 
    290 Let’s say you want to add all the files in your project directory to the staging area. Execute the following command to do the same
    291 
    292 `git add --all`
    293 
    294 
    295 
    296 
    297 
    298 
    299