You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
As an evaluator of Drupal (or an experienced dev looking for a porcelain environment) I want to be able to spin up a patchless release of the current release of Drupal.
Currently, DrupalPod states:
Open an issue page on Drupal.org to see the available options.
but I don't want to open an issue just to get an environment, and asking new users to "find an issue" might be daunting.
Describe the solution you'd like
On the "open an issue page" screen, add some text like "... or start from Drupal core." where the link takes the user to an install with the current Drupal core release and some sensible defaults:
branch: none
patch: none
core version: current release
install profile: ??? (I'd suggest standard or umami)
Describe alternatives you've considered
Alternatively, we could add a link to some placeholder issue where users can go?
Additional context
That's it. Thanks!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
As an evaluator of Drupal (or an experienced dev looking for a porcelain environment) I want to be able to spin up a patchless release of the current release of Drupal.
Currently, DrupalPod states:
but I don't want to open an issue just to get an environment, and asking new users to "find an issue" might be daunting.
Describe the solution you'd like
On the "open an issue page" screen, add some text like "... or start from Drupal core." where the link takes the user to an install with the current Drupal core release and some sensible defaults:
Describe alternatives you've considered
Alternatively, we could add a link to some placeholder issue where users can go?
Additional context
That's it. Thanks!
The text was updated successfully, but these errors were encountered: