-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathworkspace.jsonc
More file actions
52 lines (52 loc) · 1.72 KB
/
Copy pathworkspace.jsonc
File metadata and controls
52 lines (52 loc) · 1.72 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
/**
* Bit workspace configuration for the bit-git-sync example.
* Reference: https://bit.dev/reference/workspace/workspace-json
**/{
"$schema": "https://static.bit.dev/teambit/schemas/schema.json",
"teambit.workspace/workspace": {
"name": "bit-git-sync-example",
"icon": "https://static.bit.dev/brands/bit-logo-min.png",
"defaultDirectory": "components/{name}",
/**
* The scope that this repository mirrors. `setup.sh` replaces it with
* the scope that you pass to it. Example: ./setup.sh acme.shop
**/
"defaultScope": "bitdev.git-sync-demo",
"resolveAspectsFromNodeModules": true,
"resolveEnvsFromRoots": true
},
/**
* The bit version that this workspace requires. `bit-tasks/init` reads it
* and installs this version. Without it, the runner gets the latest stable
* release. That release does not have `bit ci sync`.
*
* 2.2.16 is the floor: it is the first release whose `bit ci merge` keeps a
* cross-scope lane open until every scope has released its slice
* (teambit/bit#10661). Earlier floors: 2.2.7 for the `.bitmap` heal that
* survives a stale version in the entry (teambit/bit#10652), 2.2.5 for
* cross-scope lanes, 2.0.65 for the `bit ci sync` command itself.
**/
"teambit.harmony/bit": {
"engine": "2.2.18"
},
"teambit.dependencies/dependency-resolver": {
"rootComponents": true,
"policy": {
"dependencies": {},
"peerDependencies": {}
}
},
/**
* The sync configuration that the `bit ci sync` command and the
* bit-git-sync action both read. The README explains each key.
**/
"teambit.git/ci": {
"sync": {
"lanes": [
"*"
],
"mainSync": "pr",
"onConflict": "halt"
}
}
}