Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.We need to import the data from #3565761: Export issue data for migration to git.drupalcode.org
Migration
- Put security.drupal.org into read-only mode
- Export with
drush -v migrate-issue-data --user=1 > sdo-issues.json - Run linting, make sure it passes
- Start check-notification-queue.rb on git.drupalcode.org
- Run the import
Issue fork drupalorg-3568643
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:
- security-import-fixes-2
changes, plain diff MR !481 - security-import-fixes changes, plain diff MR !480
- dev-gitlab-setup changes, plain diff MR !477
- import-fixes changes, plain diff MR !475
- security-import-data changes, plain diff MR !460
- base-url-variable changes, plain diff MR !467
- 3568643-import-security.drupal.org-issue changes, plain diff MR !450
Comments
Comment #4
drummThe initial linting phase has been deployed, so this can be tested with production data, and we can make sure all the project mismatches have been cleaned up.
The rest of the import still needs to be done.
Comment #5
drummThe
[#123]issue references will need special filtering. We don’t want www.drupal.org to try figuring them out, it has different issues. The import being built here should convert them to GitLab project#iid references, since we are importing all issues at once.Comment #24
drummThis is now running cleanly on dev
Comment #25
fjgarlin commentedGreat news! The MR looks good. I just made a minor comment on something that is probably a non-issue.
Comment #27
drumm