- 🇺🇸United States drumm NY, US
With 📌 Remove project_issue_file_test (DrupalCI) Active , DrupalCI is no longer on Drupal.org. GitLab CI can test arbitrary branches.
See #2576141: Release branches for core patch releases/release candidates → and #2268449: Run contrib module branch tests against both dev and latest stable core branches → for more discussion.
Right now only 8.[integer].x is available for testing in the DrupalCI interface.
If we wanted to do a release branch for 8.0.0, then the obvious name for that branch would be '8.0.0' - however it would not be possible to run tests against this.
@webchick experimented on staging, and found that 8.00.x works - if we think this is an acceptable workaround, it'd be good enough for me - however we'd need to ensure that once #2268449: Run contrib module branch tests against both dev and latest stable core branches → is implemented, it's available in the same way there.
1. Confirm that 8.00.x as a workaround works and is acceptable
2. Allow arbitrary branch names to show up in places like https://www.drupal.org/node/3060/qa →
Closed: outdated
3.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
With 📌 Remove project_issue_file_test (DrupalCI) Active , DrupalCI is no longer on Drupal.org. GitLab CI can test arbitrary branches.