Needs review
Project:
DrupalPod
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 May 2024 at 00:44 UTC
Updated:
13 Jul 2024 at 13:44 UTC
Jump to comment: Most recent
Problem/Motivation
The .github directory contains
- Issue Templates
- Workflows
- codesee
- vscode extension build and release (the latter that was never setup with the secret in github to publish)
- Funding and Move YAML definitions
Proposed resolution
Read https://docs.gitlab.com/ee/ci/migration/github_actions.html and implement
- Move .github/ISSUE_TEMPLATES to .gitlab/issue_templates. These won't be used currently, but maybe some day..?
- Move .github/PULL_REQUEST_TEMPLATE.md to .gitlab/merge_request_templates/merge_request.md
- Remove .github/RELEASE_NOTES_TEMPLATE.md as that does not seem to be supported by GitLab.
- Create a .gitlab-ci.yml file to migrate workflows into jobs and make sure to add the OVSX_TOKEN as a secret in GitLab.
- Ensure that GitLab forks cannot modify or access OVSX_TOKEN. This is a parent project setting.
- Ignore GitHub specific files like FUNDING.yml, codesee-arch-diagram.yml and move.yml
Remaining tasks
Issue fork drupalpod-3445277
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:
changes
Comments
Comment #2
mradcliffeComment #4
mradcliffeOkay, I have a good start.
The only thing remaining is codesee and the token setup, but we never had the token setup in GitHub anyway.
Comment #5
mradcliffeFrom the recent PRs, the CodeSee workflow isn't doing anything anyway. So maybe leaving the github workflow file there and ignoring it here in GitLab CI would be fine since GitKraken, who recently acquired CodeSee, is providing GitLab support for its DevEx platform anyway.