You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw your additions to "training material" type in dev branch. It seems that it's already functioning to some extent, but is it OK to create a new branch cambridge and keep those test-changes there? I will also put the dev into original status without those additions. This is for practical reason, that it's quite a work for merging new changes in dev from master excluding those changes.
Let's also keep the test.biii.eu at cambridge branch (= what it is now and for further testing of training material node fields), and for adding other new changes we can pull from the dev branch in test.biii.eu and merge them into cambridge.
The text was updated successfully, but these errors were encountered:
As there is no objection for two weeks, I will set test.biii.eu as the cambridge branch (as it is, in a sense but the branch name changes) and leave the dev branch for further development without test-changes in teaching material related fields.
Hi @PerrineGilloteaux
I saw your additions to "training material" type in
dev
branch. It seems that it's already functioning to some extent, but is it OK to create a new branchcambridge
and keep those test-changes there? I will also put thedev
into original status without those additions. This is for practical reason, that it's quite a work for merging new changes indev
frommaster
excluding those changes.Let's also keep the test.biii.eu at
cambridge
branch (= what it is now and for further testing of training material node fields), and for adding other new changes we can pull from thedev
branch in test.biii.eu and merge them intocambridge
.The text was updated successfully, but these errors were encountered: