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
In other words, when the --preset modifier is available, specified dependencies for the given preset are merged with the dependencies values. And preset takes precedence over dependencies.
The text was updated successfully, but these errors were encountered:
CKEditorBot
added
status:in-progress
Set automatically when an issue lands in the "In progress" column. We are working on it.
status:planned
Set automatically when an issue lands in the "Sprint backlog" column. We will be working on it soon.
and removed
status:in-progress
Set automatically when an issue lands in the "In progress" column. We are working on it.
status:planned
Set automatically when an issue lands in the "Sprint backlog" column. We will be working on it soon.
labels
Dec 2, 2022
What would be expected outcome? I imagine that ckeditor5-dev should have its commit hash saved in the preset/development object. What about the ckeditor5-linters-config though?
Its commit hash is not saved.
Its commit hash gets saved in the dependencies object.
It gets added to the preset/development object and its commit hash gets saved there.
Option 1 would mean that save does not save the exact state of the multirepo.
Option 2 would mean that default dependencies and other presets are affected.
Because of this, I come to the conclusion that correct behavior there is to add the ckeditor5-linters-config key along with its commit hash to the preset/development object.
馃摑 Provide a description of the new feature
Let's assume the following configuration as input. It uses tags, which we plan to introduce soon.
While bootstrapping the project (
mrgit sync
), mrgit clones and check-outs dependencies on the latest created tag.A package published on npm may (but it does not have to) contain the same files as a tag on Github. Fortunately, the packages specified above do.
So, by default,
sync
will process repositories specified in the#dependencies
key.Presets
Let's assume I'd like to synchronize the entire project depending on events, e.g., when starting TP, preparing a release, etc.
An example configuration.
And passing a preset name when using the
sync
command.mrgit sync
: all packages use the latest tag.mrgit sync --preset dev
: all packages are checked out on a#master
branch.mrgit sync --preset typedoc
:ckeditor5-dev
uses the#ck/11721-build-API-from-typedoc
branch, linters -@latest
.In other words, when the
--preset
modifier is available, specified dependencies for the given preset are merged with thedependencies
values. And preset takes precedence over dependencies.The text was updated successfully, but these errors were encountered: