Automated Project Update Bot fixes
3 unresolved threads
3 unresolved threads
This merge request was automatically created by the Project Update Bot. It contains the changes from run 11-109123.
Merge request reports
Activity
added 10 commits
-
8cc8db1b...4bb4c425 - 9 commits from branch
project:8.x-3.x - 8cfbbe47 - Merge branch '8.x-3.x' into 'project-update-bot-only'
-
8cc8db1b...4bb4c425 - 9 commits from branch
added 4 commits
-
5f7e6560...48f35acb - 3 commits from branch
project:8.x-3.x - 87205f97 - Merge branch jsonapi_extras:8.x-3.x into project-update-bot-only
-
5f7e6560...48f35acb - 3 commits from branch
added 2 commits
-
f3999748 - 1 commit from branch
project:8.x-3.x - 6f6be302 - Merge branch '8.x-3.x' of https://git.drupalcode.org/project/jsonapi_extras...
-
f3999748 - 1 commit from branch
16 16 # However, you can modify this template if you have additional needs for your project. 17 17 ################ 18 18 19 ################ 19 ################# 32 32 # As long as you include this, any future includes added by the Drupal Association will be accessible to your pipelines automatically. 33 33 # View these include files at https://git.drupalcode.org/project/gitlab_templates/ 34 34 ################ 35 - project: $_GITLAB_TEMPLATES_REPO 36 ref: $_GITLAB_TEMPLATES_REF 35 - project: "issue/gitlab_templates-3449621" This can't be committed as is; this is an updatebot change, right? My understanding is that updatebot fixes are supposed to be left in their own branch, and then the actual MR to upgrade to Drupal 11 should be in a different branch (for example, on this issue, the branch https://git.drupalcode.org/issue/jsonapi_extras-3425240/-/tree/3425240-automated-drupal-11-fix).
48 48 ################ 49 49 variables: 50 50 SKIP_ESLINT: '1' 51 # Ignore logo.psd file from cspell check.
Please register or sign in to reply