Problem/Motivation
Switch from DrupalCI testing to Drupal Gitlab templates.
Steps to reproduce
Proposed resolution
Remaining tasks
- Fix issues reported by cspell CI job
- Fix issues reported by eslint CI job
- Fix issues reported by stylelint CI job
- Remove all DrupalCI automated tests, when issue is fixed
User interface changes
API changes
Data model changes
Issue fork bootstrap_paragraphs-3437111
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
it-cruComment #6
it-cruComment #7
it-cru@kerrymick @thejimbirch: I've raised this to major because PHPStan found a possible issue in update path. See my changes in bp_card.install file. Maybe these changes should be cherry picked for a 5.0.1 hotfix release.
Comment #8
it-cruComment #9
thejimbirch commentedThanks IT-Cru!
Comment #10
it-cru@thejimbirch Does it also make sense to add Gitlab CI templates to 8.x-2.x branch because of current usages?
Comment #11
thejimbirch commentedYeah, that is a great idea. We plan on supporting that minimally.
Comment #12
it-cruComment #14
kerrymick commentedFixes merged.
Comment #15
it-cru@kerrymick: Should current state of 5.0.x be tagged as hotfix 5.0.1 to avoid issues for people who tries to upgrade from 8.x-2.x to 5.0.x because of this issue detected by PHPStan CI job (mentioned in #7?
I think this would be a good idea to avoid popup of follow up issues with broken upgrades.
Comment #16
thejimbirch commentedThank @IT-Cru. 5.0.1 released.