-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathworkspace.jsonc
More file actions
59 lines (59 loc) · 1.78 KB
/
Copy pathworkspace.jsonc
File metadata and controls
59 lines (59 loc) · 1.78 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
53
54
55
56
57
58
59
/**
* 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}",
/**
* `setup.sh` replaces this placeholder with the scope that you pass to it.
* Example: ./setup.sh acme.shop
**/
"defaultScope": "teambit.api-reference"
},
/**
* 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.5 is the floor for the reconciler: it is the first release that heals a
* `.bitmap` entry whose `mainFile` is no longer in git. Below it, one such
* entry halts every main sync until a human edits `.bitmap` by hand.
**/
"teambit.harmony/bit": {
"engine": "2.2.5"
},
"teambit.dependencies/dependency-resolver": {
"policy": {
"dependencies": {},
"peerDependencies": {}
}
},
/**
* The component uses the core Node env. A core env needs no install step,
* so a fresh clone has no env-resolution problem.
**/
"teambit.workspace/variants": {
"components/greeting": {
"teambit.harmony/node": {}
}
},
/**
* The sync configuration that the `bit ci sync` command and the
* bit-git-sync action both read. The README explains each key.
**/
"teambit.component/issues": {
"ignoreIssues": ["CircularDependencies"]
},
"teambit.git/ci": {
"sync": {
"lanes": [
"*"
],
"mainSync": "pr",
"onConflict": "halt"
}
}
}