In Depth Guide : Acquia Certified Developer Drupal
  • IN DEPTH GUIDE: ACQUIA CERTIFIED DEVELOPER - DRUPAL 8 EXAM
  • Test Format
  • Domain 1.0: Fundamental Web Development Concepts
    • 1.1 Demonstrate knowledge of HTML and CSS
    • 1.2 Identify Javascript and jQuery programming concepts
    • 1.3 Demonstrate the use of Git for version control
  • Domain 2.0: Site Building
    • 2.1 Demonstrate ability to create and configure Content Types with appropriate fields and field sett
    • 2.2 Demonstrate ability to configure Display Modes for building custom form and view modes for core
    • 2.3 Demonstrate ability to create and use Taxonomy vocabularies and terms for classification and org
    • 2.4 Demonstrate ability to configure Block types, manage Blocks library and configure Block layouts
    • 2.5 Demonstrate ability to build main and alternative navigation systems by using Menus
    • 2.6 Demonstrate ability to create and configure Views for building content list pages, blocks and fe
    • 2.7 Demonstrate ability to use Configuration Management capabilities for exporting site configuratio
    • 2.8 Demonstrate ability to build multilingual websites using core multilingual capabilities
    • 2.9 Demonstrate ability to build RESTful web application using core Web Services capabilities
  • Domain 3.0: Front end development (theming)
    • 3.1 Given a scenario, demonstrate ability to create a custom theme or sub theme.
    • 3.2 Demonstrate knowledge of theming concepts
    • 3.3 Demonstrate ability to use Twig syntax
    • 3.4 Demonstrate ability to build or override Twig templates for defining layout content
    • 3.5 Demonstrate ability to write template pre-process functions for overriding custom output
  • Domain 4.0: Back end development (coding)
    • 4.1 Demonstrate ability to write code using core and Object Oriented PHP
    • 4.2 Demonstrate ability to develop Custom Modules using Drupal API for extending Drupal functionalit
    • 4.3 Demonstrate ability to store and retrieve data using code
    • 4.4 Demonstrate ability to work with other essential APIs
    • 4.5 Demonstrate ability to write code using Drupal Coding Standards
    • 4.6 Demonstrate ability to analyze and resolve site performance issues arising from site configurati
    • 4.7 Demonstrate ability to analyze and resolve security issues arising from site configuration or cu
  • Other Resources
Powered by GitBook
On this page
  • Git Commands
  • You can also chain commands.
  • Git Rebase
  • For example:
  • Git Workflow
  • Other Resources
  1. Domain 1.0: Fundamental Web Development Concepts

1.3 Demonstrate the use of Git for version control

Previous1.2 Identify Javascript and jQuery programming conceptsNextDomain 2.0: Site Building

Last updated 7 years ago

Review git commands and how to commit deleted files.

is a version control system (VCS) that keeps track of history and changes t source code.

Git Commands

Review common and how they affect the code base.

  • Git clone: Creates a local version of a remote repository with user write permissions to push code back to the remote repository.

  • Git fork: Creates a separate local version of a remote repository when the user does not have direct write permissions to push code back to the remote repository.

  • Git pull: This will update the local code base from the remote repository.

  • Git fetch: This will sync the local code base from the remote repository but not make any changes to the local code base.

  • Git commit: Submits files from the local repository to the staging environment.

  • Git push: This will submit code to the remote repository.

  • Git add: Updates the working index with any local changes to be staged for the next commit. The * will add all modifications, deleted files, and new files.

You can also chain commands.

  • `git add -A && git commit -m "Your Message"`

  • `git add -A` will add all changes to the repository and `git commit -m"message"` will add your message to the repository.

Git Rebase

With git-rebase you can push local commits together into one commit (without force). With rebase, you can commit more often and then merge your commits together before pushing back to the shared repo. For simplicity, we are only going to talk about rebasing locally. This is a little more complicated to explain, so it is easier to just show a simple example.

For example:

git rebase --i

returns

# p    pick = use commit   
# r    reword = use commit, but edit the commit message   
# e    edit = use commit, but stop for amending   
# s    squash = use commit, but meld into previous commit   
# f    fixup = like "squash", but discard this commit's log message   
# x    exec = run command (the rest of the line) using shell

you can created a text file called "git-article.txt" and committed this new file. Then you can add some new text to this file and made a new commit. Use git add -p, which shows your change. Use the command y to accept this change and committed this change to the git local history. As of right now, both commits touch the same file and really, You only need one commit to represent the changes. You can then use

git rebase --interactive HEAD~2

to see both commits. Pick one commit and use command f to amend changes but discard the commit's log message. Save these changes. Then you can us git log to show recent commits. This leaves a much cleaner history. Rebasing is useful if you forgot to add something to your first commit.

Git Workflow

Gitflow is a method and branching model for git that is geared towards accountability, team collaboration and scaling development teams.

Other Resources

Code Academy Learn Git
Recommended Skillset for Using BLT
Git Docs
Git Rebase
5 ways to step up your git game
Common Git Workflows
Git
Git commands