Drush adds d.o-style .info information for my private modules, causing Drupal to then check Drupal.org for updates to them.

Not sure how best to proceed. Checking for update info on d.o for each module seems excessive. Possibly only do .info rewriting for modules that have default (d.o) git repos?

Members fund testing for the Drupal project. Drupal Association Learn more


jhedstrom’s picture

Only rewriting for d.o. seems like the way to go.

jhedstrom’s picture

Version: 7.x-5.8 » 8.x-6.x-dev
Status: Active » Needs review
871 bytes

Patch attached.

jhedstrom’s picture

Status: Needs review » Active
dkingofpa’s picture

It also causes git status and git diff to show changes in private repos when it's only the .info rewriting. It's a constant nuisance.

I was previously coming at this from the 7.x-5.x-dev version on #1890234: Do not override properties in .info files.

jhedstrom’s picture

Status: Active » Needs review
696 bytes

This should do the trick.

lotyrin’s picture

Status: Needs review » Reviewed & tested by the community

Yep. That seems adequate.

moshe weitzman’s picture

Assigned: Unassigned » jhedstrom
jhedstrom’s picture

Status: Reviewed & tested by the community » Fixed

This was actually committed back in January (764ab31d).

Status: Fixed » Closed (fixed)

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

jdillick’s picture

Does anyone think the patch from #5 might break automated build processes for peeps who rely on drush make *to* put the versions in their custom modules? Any particular reason this couldn't bale on an argument --no-gitinfofile?

This is dissappointing. A behavior change such as this, which break version based dependencies, seems inappropriate, especially at version 5.9.

jdillick’s picture

Status: Closed (fixed) » Needs review
greg.1.anderson’s picture

Status: Needs review » Closed (won't fix)
Issue tags: +needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If desired, you may copy this bug to our Github project and then post a link here to the new issue. Please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.