On almost every issue, it would be good to run the automated tests before committing, but unfortunately, Drupal.org can't automatically kickoff our Travis-CI build, so I end up creating a new branch in my personal GitHub fork of Panopoly with the patches and then paste the link into the comments.

This is super tedious and frequently error prone, and makes me groan every time I have to do it (which is a lot). :-)

So, I started writing a script that will automate this! It uses the new Drupal.org API, to pull in the list of displayed patches and determines what project they should go against based on the filename. Then it creates a new branch in Git repo which has those patches added to the drupal-org.make.

I'll attach a patch with it in a moment. I'll probably test for a few more days before committing!

Comments

dsnopek’s picture

Status: Active » Needs review
StatusFileSize
new6.42 KB

Patch is attached!

dsnopek’s picture

StatusFileSize
new6.48 KB

I already have some fixes and updates to this! New patch attached.

  • dsnopek committed c8f9f18 on 7.x-1.x
    Issue #2434607 by dsnopek: Write a script to submit issue patches to...
dsnopek’s picture

Status: Needs review » Fixed

The script has been working well for the last couple days! Commited.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.