@davidbyoung/software-factory 0.1.2 → 0.1.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +20 -20
- package/actions/factory-agent/action.yml +1 -1
- package/agents/factory-e2e-reviewer.md +102 -0
- package/agents/factory-test-reviewer.md +26 -64
- package/agents/factory-ticket-readiness.md +14 -6
- package/dist/agent/claude-code.d.mts +3 -0
- package/dist/agent/claude-code.mjs +89 -0
- package/dist/agent/index.d.mts +2 -0
- package/dist/agent/index.mjs +5 -0
- package/dist/board.mjs +1 -1
- package/dist/cli.mjs +46 -4
- package/dist/code-host/github-setup.d.mts +5 -0
- package/dist/code-host/github-setup.mjs +133 -0
- package/dist/code-host/github.mjs +4 -0
- package/dist/code-host/index.d.mts +1 -1
- package/dist/code-host/index.mjs +2 -1
- package/dist/code-host/types.d.mts +2 -0
- package/dist/commands.d.mts +16 -0
- package/dist/commands.mjs +129 -0
- package/dist/config.d.mts +87 -20
- package/dist/config.mjs +344 -89
- package/dist/deps.d.mts +7 -4
- package/dist/deps.mjs +20 -9
- package/dist/doctor.d.mts +9 -16
- package/dist/doctor.mjs +71 -68
- package/dist/explain.d.mts +4 -0
- package/dist/explain.mjs +174 -0
- package/dist/guard-commit.d.mts +7 -2
- package/dist/guard-commit.mjs +58 -21
- package/dist/init.d.mts +12 -14
- package/dist/init.mjs +194 -136
- package/dist/lib/default-branch.d.mts +35 -0
- package/dist/lib/default-branch.mjs +117 -0
- package/dist/lib/has-command.d.mts +5 -0
- package/dist/lib/has-command.mjs +8 -0
- package/dist/lib/listed.d.mts +2 -0
- package/dist/lib/listed.mjs +4 -0
- package/dist/lib/refined-check.d.mts +7 -0
- package/dist/lib/refined-check.mjs +76 -0
- package/dist/lib/work-status.d.mts +12 -2
- package/dist/lib/work-status.mjs +14 -3
- package/dist/parts.d.mts +18 -15
- package/dist/parts.mjs +15 -43
- package/dist/patch-coverage.d.mts +13 -0
- package/dist/patch-coverage.mjs +73 -0
- package/dist/poller.d.mts +20 -3
- package/dist/poller.mjs +62 -15
- package/dist/pr-watch.d.mts +3 -2
- package/dist/pr-watch.mjs +22 -5
- package/dist/pr.mjs +34 -2
- package/dist/remove.d.mts +11 -0
- package/dist/remove.mjs +156 -0
- package/dist/runner/github-actions.d.mts +1 -1
- package/dist/runner/github-actions.mjs +12 -0
- package/dist/runner/index.d.mts +1 -1
- package/dist/runner/index.mjs +2 -1
- package/dist/runner/setup.d.mts +2 -0
- package/dist/runner/setup.mjs +22 -0
- package/dist/runner/types.d.mts +3 -0
- package/dist/runner/types.mjs +0 -2
- package/dist/session-start.d.mts +23 -13
- package/dist/session-start.mjs +56 -44
- package/dist/setup.d.mts +98 -0
- package/dist/setup.mjs +3 -0
- package/dist/site/servers.d.mts +6 -2
- package/dist/site/servers.mjs +14 -9
- package/dist/site.mjs +2 -2
- package/dist/status.d.mts +4 -4
- package/dist/status.mjs +8 -7
- package/dist/sync.d.mts +26 -2
- package/dist/sync.mjs +177 -13
- package/dist/ticket.mjs +19 -1
- package/dist/tickets/github-setup.d.mts +2 -0
- package/dist/tickets/github-setup.mjs +50 -0
- package/dist/tickets/github.mjs +0 -2
- package/dist/tickets/index.mjs +2 -1
- package/dist/tickets/transport.mjs +1 -3
- package/dist/tickets/types.mjs +0 -2
- package/dist/tool-names.d.mts +11 -0
- package/dist/tool-names.mjs +20 -0
- package/dist/tools.d.mts +56 -0
- package/dist/tools.mjs +76 -0
- package/docs/builds.md +111 -59
- package/docs/cli.md +106 -69
- package/docs/configuration.md +489 -171
- package/docs/design.md +18 -5
- package/docs/developing.md +179 -73
- package/docs/existing-repo.md +25 -12
- package/docs/github/by-hand.md +334 -0
- package/docs/github/reference.md +76 -67
- package/docs/github/setup.md +105 -286
- package/docs/glossary.md +18 -7
- package/docs/limitations.md +39 -12
- package/docs/plugins.md +305 -56
- package/docs/quick-start.md +85 -100
- package/docs/removing.md +37 -17
- package/docs/skills.md +121 -62
- package/docs/updating.md +150 -9
- package/docs/workflow.md +23 -19
- package/package.json +1 -1
- package/poller.Dockerfile +10 -18
- package/review.md +20 -11
- package/rules.md +36 -30
- package/settings.schema.json +313 -69
- package/skills/factory-address-review/SKILL.md +50 -30
- package/skills/factory-build/SKILL.md +76 -23
- package/skills/factory-deps/SKILL.md +46 -21
- package/skills/factory-design/SKILL.md +17 -8
- package/skills/factory-diagnose/SKILL.md +22 -20
- package/skills/factory-mutate/SKILL.md +38 -24
- package/skills/factory-refine/SKILL.md +55 -31
- package/skills/factory-resolve-conflicts/SKILL.md +76 -34
- package/skills/factory-trace/SKILL.md +80 -0
- package/workflows/factory-build.yml +6 -5
- package/workflows/factory-conflicts.yml +8 -8
- package/workflows/factory-deps-auto-merge.yml +3 -2
- package/workflows/factory-deps.yml +1 -1
- package/workflows/factory-poller.yml +46 -0
- package/workflows/factory-review.yml +1 -1
- package/skills/factory-address-review/patch-coverage.py +0 -68
package/docs/quick-start.md
CHANGED
|
@@ -1,33 +1,26 @@
|
|
|
1
1
|
# Quick start
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
3
|
+
For someone with a repository and a coding agent who has never used the
|
|
4
|
+
factory. At the end you have a pull request built from one of your
|
|
5
|
+
tickets. You run a few commands, say how your code is checked, write one
|
|
6
|
+
ticket, and answer a question or two. It needs no board, no secrets, and
|
|
7
|
+
nothing to host.
|
|
7
8
|
|
|
8
|
-
A word you do not know is in the [glossary](glossary.md).
|
|
9
|
-
_[Planned](developing.md#what-is-built)_ is not built yet, and says what to
|
|
10
|
-
do until then.
|
|
9
|
+
A word you do not know is in the [glossary](glossary.md).
|
|
11
10
|
|
|
12
11
|
## You need
|
|
13
12
|
|
|
14
13
|
- A repository on a supported code host, cloned on your machine, with the
|
|
15
14
|
code host's command-line tool signed in.
|
|
16
15
|
- A supported coding agent, signed in.
|
|
17
|
-
- Node 22.18 or later.
|
|
16
|
+
- Node 22.18 or later.
|
|
18
17
|
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
Your repository does not have to be JavaScript. If it is not, read
|
|
23
|
-
[this section](existing-repo.md#a-repository-that-is-not-javascript)
|
|
24
|
-
first: installing adds a small `package.json`.
|
|
18
|
+
[What you need](github/setup.md#what-you-need) names the supported tools
|
|
19
|
+
and how to check each. A repository with no `package.json` works too:
|
|
20
|
+
[read this first](existing-repo.md#a-repository-that-is-not-javascript).
|
|
25
21
|
|
|
26
22
|
## 1. Install
|
|
27
23
|
|
|
28
|
-
_[Planned](developing.md#what-is-built)._ Until the package is published,
|
|
29
|
-
it cannot be installed outside the repository it is developed in.
|
|
30
|
-
|
|
31
24
|
Once on your machine, so you can type `factory`:
|
|
32
25
|
|
|
33
26
|
```bash
|
|
@@ -41,8 +34,7 @@ npm install --save-dev @davidbyoung/software-factory
|
|
|
41
34
|
```
|
|
42
35
|
|
|
43
36
|
**It worked when** `factory`, run in your repository, prints the list of
|
|
44
|
-
its commands.
|
|
45
|
-
expected.
|
|
37
|
+
its commands.
|
|
46
38
|
|
|
47
39
|
## 2. Set it up
|
|
48
40
|
|
|
@@ -50,50 +42,47 @@ expected.
|
|
|
50
42
|
factory init
|
|
51
43
|
```
|
|
52
44
|
|
|
53
|
-
It
|
|
54
|
-
|
|
55
|
-
|
|
45
|
+
It shows what it found and asks which optional parts you want. For this
|
|
46
|
+
first ticket, uncheck every part. It then lists everything it will do, and
|
|
47
|
+
once you tell it to go ahead, writes your settings file,
|
|
48
|
+
`.claude/factory.yaml`, and the instructions and checks your coding agent
|
|
49
|
+
follows. It commits nothing. [What it changes](removing.md) lists every
|
|
50
|
+
file.
|
|
56
51
|
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
adds hooks: small checks your agent runs on its own, such as refusing a
|
|
60
|
-
commit on your main branch. It adds one line to your agent's instructions
|
|
61
|
-
file, such as `CLAUDE.md`, and the hooks to your agent's settings,
|
|
62
|
-
creating either file if you have none. It changes nothing else of yours,
|
|
63
|
-
and commits nothing. [What it changes](removing.md) lists every item and
|
|
64
|
-
how to undo it.
|
|
52
|
+
**It worked when** the checks `init` prints last all show ✓, or `-` for a
|
|
53
|
+
part you left off. `factory doctor` runs them again at any time.
|
|
65
54
|
|
|
66
|
-
**
|
|
67
|
-
|
|
55
|
+
**Then say how a change is checked.** `init` ends with a list headed "Left
|
|
56
|
+
to do", and one line of it comes before your first build:
|
|
68
57
|
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
```yaml
|
|
73
|
-
version: 1
|
|
74
|
-
repository: your-name/your-repo
|
|
75
|
-
```
|
|
76
|
-
|
|
77
|
-
```bash
|
|
78
|
-
factory sync
|
|
58
|
+
```text
|
|
59
|
+
Add the commands that check a change, under commands.gate in .claude/factory.yaml
|
|
79
60
|
```
|
|
80
61
|
|
|
81
|
-
A build
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
linter, list it under `before-commit` in the settings file:
|
|
62
|
+
A build runs these commands, in order, before it opens its pull request,
|
|
63
|
+
and cannot finish without them. Add
|
|
64
|
+
[`commands.gate`](configuration.md#commandsgate) to
|
|
65
|
+
`.claude/factory.yaml`, with your own test and lint commands in place of
|
|
66
|
+
these:
|
|
87
67
|
|
|
88
68
|
```yaml
|
|
89
|
-
|
|
90
|
-
|
|
69
|
+
commands:
|
|
70
|
+
# What a build runs to check its change, in order.
|
|
71
|
+
gate:
|
|
72
|
+
- npm test
|
|
73
|
+
- npm run lint
|
|
91
74
|
```
|
|
92
75
|
|
|
76
|
+
A repository with no tests yet lists the checks it does have, such as a
|
|
77
|
+
formatter or a compile, and adds its tests to the gate when there are
|
|
78
|
+
some.
|
|
79
|
+
|
|
80
|
+
**It worked when** `factory gate` runs each command and ends without a
|
|
81
|
+
line that starts `gate failed on`.
|
|
82
|
+
|
|
93
83
|
## 3. Merge the setup
|
|
94
84
|
|
|
95
|
-
Commit what `
|
|
96
|
-
it on your code host, as for any change, and merge it:
|
|
85
|
+
Commit what `init` wrote on a branch and push it:
|
|
97
86
|
|
|
98
87
|
```bash
|
|
99
88
|
git switch -c set-up-factory
|
|
@@ -102,24 +91,26 @@ git commit -m "Set up the software factory"
|
|
|
102
91
|
git push -u origin set-up-factory
|
|
103
92
|
```
|
|
104
93
|
|
|
105
|
-
|
|
94
|
+
Open a pull request for the branch on your code host and merge it, as for
|
|
95
|
+
any change. Then bring your default branch up to date. Here it is called
|
|
96
|
+
`main`:
|
|
106
97
|
|
|
107
98
|
```bash
|
|
108
99
|
git switch main
|
|
109
100
|
git pull
|
|
110
101
|
```
|
|
111
102
|
|
|
112
|
-
|
|
113
|
-
|
|
103
|
+
Start a new session of your coding agent, which loads the factory from the
|
|
104
|
+
files now in your repository.
|
|
114
105
|
|
|
115
106
|
**It worked when** the new session, asked which skills it has, lists
|
|
116
|
-
`factory-refine` and `factory-build`.
|
|
117
|
-
one kind of job, such as refining a ticket.
|
|
107
|
+
`factory-refine` and `factory-build`.
|
|
118
108
|
|
|
119
109
|
## 4. Open a ticket
|
|
120
110
|
|
|
121
|
-
|
|
122
|
-
|
|
111
|
+
Open a ticket in your ticket system: on GitHub, an issue in your
|
|
112
|
+
repository. Say three things: what you want, why, and how you will know it
|
|
113
|
+
is done. A few sentences is enough.
|
|
123
114
|
|
|
124
115
|
```text
|
|
125
116
|
Title: Show the opening hours in the footer
|
|
@@ -128,17 +119,17 @@ The hours are only on the contact page, and people ask for them.
|
|
|
128
119
|
Done when: every page's footer shows the same hours the contact page does.
|
|
129
120
|
```
|
|
130
121
|
|
|
131
|
-
|
|
122
|
+
**It worked when** the ticket has a number. This page uses 12.
|
|
132
123
|
|
|
133
124
|
## 5. Refine it
|
|
134
125
|
|
|
135
|
-
In
|
|
126
|
+
In the session, say:
|
|
136
127
|
|
|
137
128
|
```text
|
|
138
129
|
refine ticket 12
|
|
139
130
|
```
|
|
140
131
|
|
|
141
|
-
The session reads the ticket and the code it touches
|
|
132
|
+
The session reads the ticket and the code it touches, then asks you the
|
|
142
133
|
decisions that are yours, each as a choice with its recommendation first:
|
|
143
134
|
|
|
144
135
|
```text
|
|
@@ -148,8 +139,7 @@ Where should the hours come from?
|
|
|
148
139
|
```
|
|
149
140
|
|
|
150
141
|
**It worked when** the ticket ends with acceptance criteria, a checklist
|
|
151
|
-
|
|
152
|
-
build.
|
|
142
|
+
of exactly what "done" means, and the session says it is ready to build.
|
|
153
143
|
|
|
154
144
|
## 6. Build it
|
|
155
145
|
|
|
@@ -159,22 +149,14 @@ In the same session, or a new one:
|
|
|
159
149
|
build ticket 12
|
|
160
150
|
```
|
|
161
151
|
|
|
162
|
-
Telling a session to build a ticket is how you approve it.
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
1. comments on the ticket that it has claimed it, so no other session
|
|
167
|
-
builds the same one;
|
|
168
|
-
2. makes a branch;
|
|
169
|
-
3. writes a test, then the change;
|
|
170
|
-
4. checks each commit with your `before-commit` commands, if you set any;
|
|
171
|
-
5. opens a pull request that closes the ticket, as a draft, which tells
|
|
172
|
-
people and the automated review it is not finished;
|
|
173
|
-
6. marks it ready for review once your CI passes on it, or after two
|
|
174
|
-
minutes when no CI runs on it, and answers any review it gets.
|
|
152
|
+
Telling a session to build a ticket is how you approve it. The session
|
|
153
|
+
makes a branch, writes a test and then the change, and opens a pull
|
|
154
|
+
request that closes the ticket. Expect minutes, not seconds.
|
|
155
|
+
[Workflow](workflow.md#from-a-ticket-to-a-merge) has each step.
|
|
175
156
|
|
|
176
157
|
**It worked when** its last message names the pull request, says what it
|
|
177
|
-
built, and says how it checked it.
|
|
158
|
+
built, and says how it checked it. This page uses 15 for the pull
|
|
159
|
+
request's number.
|
|
178
160
|
|
|
179
161
|
## 7. Read it and merge
|
|
180
162
|
|
|
@@ -189,34 +171,37 @@ answer your comments:
|
|
|
189
171
|
address the review on pull request 15
|
|
190
172
|
```
|
|
191
173
|
|
|
174
|
+
**It worked when** the pull request is merged and ticket 12 is closed.
|
|
192
175
|
That is the whole loop: **ticket, refine, build, read, merge.**
|
|
193
176
|
|
|
194
177
|
## If something goes wrong
|
|
195
178
|
|
|
196
|
-
| What happened
|
|
197
|
-
|
|
|
198
|
-
| A
|
|
199
|
-
| The session stops and says it needs you
|
|
200
|
-
| The
|
|
201
|
-
|
|
|
202
|
-
|
|
|
203
|
-
|
|
|
204
|
-
|
|
|
179
|
+
| What happened | What to do |
|
|
180
|
+
| ---------------------------------------------- | ------------------------------------------------------------------------------------------- |
|
|
181
|
+
| A test or a check fails during the build | Nothing. The session sees the output, fixes the cause, and tries again |
|
|
182
|
+
| The session stops and says it needs you | It says why, in the session and on the ticket. Answer, then ask it to build ticket 12 again |
|
|
183
|
+
| The build stops on `commands.gate is not set` | Add your test and lint commands, as in step 2, then ask it to build ticket 12 again |
|
|
184
|
+
| The session was closed or crashed partway | Ask a new session to build ticket 12. It picks up the branch it made |
|
|
185
|
+
| You want to change what was decided | Ask a session to refine ticket 12 again, or edit the ticket |
|
|
186
|
+
| CI fails on the pull request | Ask a session to address the review on pull request 15. It reads the failure and fixes it |
|
|
187
|
+
| The session does not know the factory's skills | The setup is not merged, or the session started before it was. See step 3 |
|
|
188
|
+
| Anything else | Run `factory doctor`. It says what is wrong, and what to do about it |
|
|
205
189
|
|
|
206
190
|
## What to add next
|
|
207
191
|
|
|
208
|
-
Everything above runs on your machine while you watch. Each
|
|
192
|
+
Everything above runs on your machine while you watch. Each of these is
|
|
209
193
|
optional, stands alone, and can come later.
|
|
210
194
|
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
221
|
-
|
|
222
|
-
|
|
195
|
+
- **An automated review, a board, builds in the cloud, builds that start
|
|
196
|
+
from the board, and pull requests that merge themselves.** Run
|
|
197
|
+
`factory init` again and check the parts you want. It asks for a token
|
|
198
|
+
or two and sets everything else up.
|
|
199
|
+
[Setting up on GitHub](github/setup.md#run-factory-init) says what each
|
|
200
|
+
part gives you and what it asks.
|
|
201
|
+
- **A command before every commit a session makes,** such as your linter:
|
|
202
|
+
a few lines under
|
|
203
|
+
[`commands.before-commit`](configuration.md#commandsbefore-commit).
|
|
204
|
+
- **Your own reviewers,** so a change to your content or your design is
|
|
205
|
+
read by an expert agent: a few lines under
|
|
206
|
+
[`plugins`](configuration.md#plugins), which [Plug-ins](plugins.md)
|
|
207
|
+
walks through.
|
package/docs/removing.md
CHANGED
|
@@ -12,8 +12,8 @@ hook, label, and setting.
|
|
|
12
12
|
lock file beside it; its own skills, agents, rules, and CI workflows, all
|
|
13
13
|
named `factory-...`; one line in your agent's instructions file that
|
|
14
14
|
imports its rules; and a few hooks in your agent's settings that guard
|
|
15
|
-
every session. If you had no `package.json`,
|
|
16
|
-
|
|
15
|
+
every session. If you had no `package.json`, you made a small one to install the factory
|
|
16
|
+
with.
|
|
17
17
|
- **On your code host:** the secrets you create for the parts you turn on;
|
|
18
18
|
the labels and statuses that say who merges a pull request and whether
|
|
19
19
|
the automated review found it ready; comments on the tickets it works;
|
|
@@ -22,22 +22,19 @@ hook, label, and setting.
|
|
|
22
22
|
Cost, which `factory init` adds when the board lacks
|
|
23
23
|
them, and the board's own Status, which the sync sets. `init` adds any of
|
|
24
24
|
the six columns the board lacked.
|
|
25
|
-
- **Outside both,** only if
|
|
26
|
-
|
|
25
|
+
- **Outside both,** only if you host the poller: the poller, wherever you
|
|
26
|
+
host it. `factory remove` names it in what is left by hand.
|
|
27
27
|
|
|
28
28
|
## What it never touches
|
|
29
29
|
|
|
30
30
|
Your code, your tickets, and your pull requests. Your own skills, agents,
|
|
31
31
|
plug-ins, and CI workflows, which the factory never writes to.
|
|
32
32
|
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
33
|
+
One file belongs to you, and removing the factory leaves it: the review
|
|
34
|
+
notes you write for the automated review. The review's workflow is the
|
|
35
|
+
factory's: every sync rewrites it, and removing the factory deletes it.
|
|
36
36
|
|
|
37
|
-
## Removing it
|
|
38
|
-
|
|
39
|
-
Until `factory remove` is built, delete by hand what
|
|
40
|
-
[the reference](github/reference.md#what-setup-adds) lists.
|
|
37
|
+
## Removing it
|
|
41
38
|
|
|
42
39
|
```bash
|
|
43
40
|
factory remove
|
|
@@ -47,16 +44,38 @@ factory remove
|
|
|
47
44
|
npm uninstall @davidbyoung/software-factory
|
|
48
45
|
```
|
|
49
46
|
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
47
|
+
If you installed the `factory` command on your machine and no longer want
|
|
48
|
+
it anywhere:
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
npm uninstall -g @davidbyoung/software-factory
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
The first command shows every file it will delete or change and asks
|
|
55
|
+
before changing anything. It then deletes the factory's files, takes its
|
|
56
|
+
hooks and its import line out of the files it shares with your coding
|
|
57
|
+
agent, and prints what is left outside the repository for you to remove by
|
|
58
|
+
hand: secrets, the rule that requires the review's verdict, labels, and the
|
|
59
|
+
board's fields. Each tool you use adds its own lines to that list. It
|
|
60
|
+
commits nothing. Review the changes, commit them on a branch, and merge.
|
|
61
|
+
|
|
62
|
+
If your settings file is gone or cannot be read, it says so, removes what
|
|
63
|
+
it finds, and names what the tools it ships with leave behind.
|
|
64
|
+
|
|
65
|
+
It leaves `package.json`, `package-lock.json`, `node_modules/` in your
|
|
66
|
+
`.gitignore`, and the setting that turns off your agent's lines naming
|
|
67
|
+
itself in commits and pull requests. The second command takes the
|
|
68
|
+
factory's entry out of `package.json`; delete the rest if nothing else
|
|
69
|
+
uses them, as [the reference](github/reference.md#what-setup-adds) says
|
|
70
|
+
for each. If you delete `package.json` and remove the `.gitignore` line,
|
|
71
|
+
delete the `node_modules/` folder too, and any file setup made that is now
|
|
72
|
+
empty, such as `.gitignore` or `.claude/settings.json`.
|
|
54
73
|
|
|
55
74
|
## Before you remove it
|
|
56
75
|
|
|
57
76
|
- **If builds are running,** let them finish or stop them first. Open
|
|
58
77
|
tickets and pull requests stay exactly as they are.
|
|
59
|
-
- **If you made the review's verdict a required check** on your
|
|
78
|
+
- **If you made the review's verdict a required check** on your default
|
|
60
79
|
branch, remove that requirement first, or every pull request waits on it
|
|
61
80
|
forever.
|
|
62
81
|
- **Deleting a label removes it from every ticket.** Keep the labels if
|
|
@@ -73,4 +92,5 @@ Each optional part can be turned off by itself. Remove its key from
|
|
|
73
92
|
factory sync
|
|
74
93
|
```
|
|
75
94
|
|
|
76
|
-
That deletes the CI workflows
|
|
95
|
+
That deletes the CI workflows only that part uses. Delete its secret
|
|
96
|
+
afterward.
|