Skip to content
Snippets Groups Projects
Select Git revision
  • 3b1f85aa34c6dde064f82bb94396f42592ef18d6
  • 11.x default protected
  • 11.2.x protected
  • 10.5.x protected
  • 10.6.x protected
  • 11.1.x protected
  • 10.4.x protected
  • 11.0.x protected
  • 10.3.x protected
  • 7.x protected
  • 10.2.x protected
  • 10.1.x protected
  • 9.5.x protected
  • 10.0.x protected
  • 9.4.x protected
  • 9.3.x protected
  • 9.2.x protected
  • 9.1.x protected
  • 8.9.x protected
  • 9.0.x protected
  • 8.8.x protected
  • 10.5.1 protected
  • 11.2.2 protected
  • 11.2.1 protected
  • 11.2.0 protected
  • 10.5.0 protected
  • 11.2.0-rc2 protected
  • 10.5.0-rc1 protected
  • 11.2.0-rc1 protected
  • 10.4.8 protected
  • 11.1.8 protected
  • 10.5.0-beta1 protected
  • 11.2.0-beta1 protected
  • 11.2.0-alpha1 protected
  • 10.4.7 protected
  • 11.1.7 protected
  • 10.4.6 protected
  • 11.1.6 protected
  • 10.3.14 protected
  • 10.4.5 protected
  • 11.0.13 protected
41 results

common.inc

Blame
  • Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    example.gitignore 1.46 KiB
    # This file contains default .gitignore rules. To use it, copy it to .gitignore,
    # and it will cause files like your settings.php and user-uploaded files to be
    # excluded from Git version control. This is a common strategy to avoid
    # accidentally including private information in public repositories and patch
    # files.
    #
    # Because .gitignore can be specific to your site, this file has a different
    # name; updating Drupal core will not override your custom .gitignore file.
    
    # Ignore core when managing all of a project's dependencies with Composer
    # including Drupal core.
    # core
    
    # Ignore dependencies that are managed with Composer.
    # Generally you should only ignore the root vendor directory. It's important
    # that core/assets/vendor and any other vendor directories within contrib or
    # custom module, theme, etc., are not ignored unless you purposely do so.
    /vendor/
    
    # Ignore configuration files that may contain sensitive information.
    sites/*/settings*.php
    sites/*/services*.yml
    
    # Ignore paths that contain user-generated content.
    sites/*/files
    sites/*/private
    
    # Ignore multi-site test environment.
    sites/simpletest
    
    # If you prefer to store your .gitignore file in the sites/ folder, comment
    # or delete the previous settings and uncomment the following ones, instead.
    
    # Ignore configuration files that may contain sensitive information.
    # */settings*.php
    
    # Ignore paths that contain user-generated content.
    # */files
    # */private
    
    # Ignore multi-site test environment.
    # simpletest