Skip to content

Instantly share code, notes, and snippets.

View weitzman's full-sized avatar

Moshe Weitzman weitzman

View GitHub Profile
@weitzman
weitzman / gist:1276540
Created October 10, 2011 21:07
Contributing to Drupal

Contributing Code to Drupal Core

  • Ideas are cultivated via
    • Blog posts on Drupal Planet
    • Working groups on groups.drupal.org
  • Large changes often have an 'Request for Comment' phase
  • Anyone may submit a patch to issue queue
  • Someone else has to review and "RTBC" it
  • Committers: Dries, catch, webchick
diff --git a/includes/mail.inc b/includes/mail.inc
index 83be066..986fb42 100644
--- a/includes/mail.inc
+++ b/includes/mail.inc
@@ -560,13 +560,18 @@ function project_issue_mail_generate_followup_mail_body($node, $history, $displa
'label' => $fields['updator'],
);
- $summary = theme('project_issue_mail_summary', $entry, $node, $comment_changes, $display_files);
+ // Append the metadata which has changed.
<?php
/**
* @file
*
* drush_phpstorm.drush.inc
*
* Generates a command XML file for PHPStorm/WebStorm/IntelliJ IDEs
* that provides integration with Drush
*/
<?php
/**
* @file
*
* Generates a command XML file for PHPStorm/WebStorm/IntelliJ IDEs
* that provides integration with Drush
*/
/**
In conjunction with *HYPERLINK NEEDED*Wednesday's Drupal Contribution Ladder session, opportunities throughout the week in a smaller setting are being offered to meet Drupal contributors that help oversee the development of Drupal core. You will climb the ladder for their subsystem, and author lessons for future Drupal contributors.
For the first part of the session, the maintainer will give a brief overview of their Drupal subsystem or project, its current progress, upcoming roadmap, and how folks can get involved. For the remaining part of the session, attendees will contribute to the presenter's core Drupal component or initiative through various hands-on activities offered by the Drupal Contribution Ladder.
Dialogue may cover topics like:
What are some common myths or oversights around their project goals?
What are concepts folks often are confused by?
What are some good learning resources out there?
And how can community members contribute a lesson plan back to "the ladder?"
@weitzman
weitzman / gist:b5de6ab86ac1ff07e9ae
Created October 17, 2014 18:12
config-rsync - not yet tested
/*
* Command callback.
*/
function drush_config_rsync() {
// Some boring option init stuff.
$backend_options = array('integrate' => TRUE);
$global_options = drush_redispatch_get_options() + array(
'strict' => 0,
);
if (drush_get_context('DRUSH_SIMULATE')) {
@weitzman
weitzman / MigrationIsRunning.php
Created April 20, 2017 14:12
Determine if a migration is running
<?php
namespace Drupal\ras_comments;
use Drupal\migrate\Event\MigrateEvents;
use Drupal\migrate\Event\MigrateImportEvent;
use Symfony\Component\EventDispatcher\EventSubscriberInterface;
/**
@weitzman
weitzman / drush8
Created May 12, 2017 15:30
drush8 wrapper when inside a a drush9 composer project. This didn't work out due to Drush8's finder finding drush9 anyway.
#!/usr/bin/env sh
SELF_DIRNAME="`dirname -- "$0"`"
PATH=$SELF_DIRNAME:$PATH DRUSH_FINDER_SCRIPT="foo" drush.phar "$@"
Outside the VM
In PHPStorm,
Run => Start Listening for PHP Connections
Run => Break at first line in PHP scripts
Inside the VM
Navigate to docroot and run:
XDEBUG_CONFIG="idekey=phpstorm remote_host=`netstat -rn | grep "^0.0.0.0 " | tr -s ' ' | cut -d " " -f2`" php -dzend_extension=xdebug.so -d xdebug.remote_enable=1 ../vendor/bin/drush st
Sets the XDEBUG_CONFIG environment variable. The value has two components:
@weitzman
weitzman / # php56 - 2017-05-08_16-14-13.txt
Created June 7, 2017 14:43
php56 (homebrew/php/php56) on macOS 10.11.6 - Homebrew build logs
Homebrew build logs for homebrew/php/php56 on macOS 10.11.6
Build date: 2017-05-08 16:14:13