search

dpc-sdp / tide

Tide is an API first, headless content management system custom built on Drupal to suit government needs.
https://github.com/dpc-sdp/tide#about
GNU General Public License v2.0
9 stars 5 forks source link

[SRM-526] Added new ci config to update reference branch. #185

Closed MdNadimHossain closed 1 year ago

MdNadimHossain commented 1 year ago

JIRA

https://digital-vic.atlassian.net/browse/SRM-526

Motivation

Reference site composer needs to keep itself updated to with the latest develop of tide modules. But pointing to develop and creating aliases in the root composer of content-reference will create conflict issue after every release with difference version. So creating a reference branch on tide profile and tide_* modules and updating this reference branch with develop branch changes every time there is a merge in develop, will solve the conflicting issue. So in the content reference root composer, just use this tide profile branch named reference.

Changes

Added a CI job, which will get triggered only for develop branch on every build and it will merge the changes from develop branch to the reference branch. This way we do not have to maintain this branch manually and it will be always up to date with develop and content-reference will be using this to get all the latest changes from develop.

anthony-malkoun commented 1 year ago

I really wanted to make something like this work...

cat composer.json| gojq '.require | with_entries(select( .key | test("^dpc"))) | map_values("dev-reference")'
MdNadimHossain commented 1 year ago

I really wanted to make something like this work...

cat composer.json| gojq '.require | with_entries(select( .key | test("^dpc"))) | map_values("dev-reference")'

Hey @anthony-malkoun I have tried this way, but the outcome is inconsistent, it removes the other things which are outside of require. So keeping the one that is already added for now. Thanks