My own basic Git cheat sheet

Git Cheat Sheet

  • Create
    • Clone Repository: git clone url
    • Create new local repository: git init
  • Local Changes
    • Detect pending changes: git status
    • Add files to commit: git add -p <filename> or git add .
    • Commit code: git commit -a -m “Comment”
    • Get code: git pull
    • Push changes: git push
    • View History: git logĀ  / git log -p <filename>
    • History/Blame: git blame <filename>
  • Branches, Merge & Rebase
    • Detect current branch: git branch
    • List all branches: git branch -av
    • Merge branch into current head: git merge <branch>
    • Rebase current head onto <branch>: git rebase <branch>

Git workflow:


PowerShell Modules: All you need to remember


Script Modules

A script module is a file (.psm1) that contains any valid Windows PowerShell code. Script developers and administrators can use this type of module to create modules whose members include functions, variables, and more.

Binary Modules

A binary module is a .NET Framework assembly (.dll) that contains compiled code. Cmdlet developers can use this type of module to create modules that contain cmdlets, providers, and more. (Existing snap-ins can also be used as binary modules.)

Manifest Modules

A manifest module is a module that includes a manifest (described later in this section) to describe its components, but that does not specify a root module in the manifest. A module manifest does not specify a root module when the ModuleToProcess key of the manifest is blank. In most cases, a manifest module also includes one or more nested modules using script modules or binary modules. A manifest module that does not include any nested modules can be used when you want a convenient way to load assemblies, types, or formats.

Dynamic Modules

A dynamic module is a module that does not persist to disk. This type of module enables a script to create a module on demand that does not need to be loaded or saved to persistent storage. By default, dynamic modules created with the New-Module cmdlet (described in the following sections) are intended to be short-lived and therefore cannot be accessed by the Get-Module cmdlet