At the moment, we create PRs on the CivicTheme development repository: https://github.com/civictheme/monorepo-drupal
When changes are accepted there we publish those changes to the https://git.drupalcode.org/project/civictheme/tree/1.x
This creates a dislocation between Drupal community and development work
This ticket to create discussion and begin moving to an improved contribution model.
1. Drupal theme commits are made via MR to the Gitlab infrastructure and invert the source of truth for the development process.
1. Create gitlab actions that publish back to the GitHub development repository (inverting the current flow)
Active
1.9
Code
GitHub was setup initially to allow running advanced CI pipelines to leverage advanced testing.
How exactly this inverted approach going to achieve the same? GitLab does not allow 11 CI jobs with customisations.
So this is not about technical reverting the flood code but rather a significant change to the development and testing process.