#DDEV

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

When contributing to fix an issue, we usually need to clone the corresponding forked issue branch on GitLab
(for example: this one). Because of this, I think the ddev drupal-get-module command might benefit from an additional parameter—not just the "version," but also one to specify the issue forked branch. That way, contributors (not only maintainers) could more easily work on open issues.

Maybe I’m stretching the purpose of the ddev command a bit, but I find it really helpful to have two remotes set up like this:

ai-3532795  git@git.drupal.org:issue/ai-3532795.git (fetch)
ai-3532795  git@git.drupal.org:issue/ai-3532795.git (push)
origin      git@git.drupal.org:project/ai.git (fetch)
origin      git@git.drupal.org:project/ai.git (push)

• origin: so I can rebase my branch on 1.2.x and pull in the latest community changes.
• ai-3532795: so I can push my own changes to the issue fork.

What do you think?