@hurshb50/setup-ubuntu 2.0.1 → 2.0.2
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.
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: draft-pr
|
|
3
|
+
description: Create draft pull requests while preserving Git stack structure.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Draft PR
|
|
7
|
+
|
|
8
|
+
Create draft PRs using repository conventions.
|
|
9
|
+
|
|
10
|
+
## Relevant commands
|
|
11
|
+
|
|
12
|
+
- `gh pr list`: Find nearby PRs.
|
|
13
|
+
- `gh pr view`: Inspect PR details.
|
|
14
|
+
- `gh pr create --draft`: Create a draft.
|
|
15
|
+
- `gh pr edit`: Update PR details.
|
|
16
|
+
- `gh pr ready --undo`: Restore draft status.
|
|
17
|
+
- `gh stack view`: Inspect the stack.
|
|
18
|
+
- `gh stack link`: Link existing PRs.
|
|
19
|
+
- `gh stack rebase`: Rebase stack branches.
|
|
20
|
+
- `gh stack push`: Push stack branches.
|
|
21
|
+
- `gh stack submit`: Create or update stack PRs.
|
|
22
|
+
|
|
23
|
+
Check `gh --help`, `gh pr --help`, or `gh stack --help` when needed. Check subcommand help before using unfamiliar options.
|
|
24
|
+
|
|
25
|
+
## Draft status
|
|
26
|
+
|
|
27
|
+
Draft status belongs to each PR, not its stack.
|
|
28
|
+
|
|
29
|
+
- Draft only PRs explicitly requested as drafts.
|
|
30
|
+
- Preserve every existing PR's current status.
|
|
31
|
+
- Never convert an entire stack to drafts.
|
|
32
|
+
- Before stack commands, verify their draft-status behavior.
|
|
33
|
+
- Ask before any command could change other PR statuses.
|
|
34
|
+
|
|
35
|
+
## Workflow
|
|
36
|
+
|
|
37
|
+
- Inspect branch and working-tree state.
|
|
38
|
+
- Identify the intended base branch.
|
|
39
|
+
- Review nearby PR titles and descriptions.
|
|
40
|
+
- Split changes into stacked PRs when requested.
|
|
41
|
+
- Preserve user changes and uncommitted work.
|
|
42
|
+
- Ask before committing changes.
|
|
43
|
+
- Do not use `gh stack submit` unless requested.
|
|
44
|
+
- Verify titles, bases, and draft status.
|
|
45
|
+
- Report PRs and stack links.
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: test-planning
|
|
3
|
+
description: Plan reliable, behavior-focused tests without implementing them.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Test Planning
|
|
7
|
+
|
|
8
|
+
Plan tests for a selected function or class.
|
|
9
|
+
|
|
10
|
+
- Inspect behavior and relevant callers.
|
|
11
|
+
- Check nearby tests for conventions.
|
|
12
|
+
- Focus on observable outcomes.
|
|
13
|
+
- Suggest representative inputs and expected results.
|
|
14
|
+
- Include important edge cases and errors.
|
|
15
|
+
- Identify uncontrolled or nondeterministic inputs.
|
|
16
|
+
- Recommend ways to control relevant inputs.
|
|
17
|
+
- Avoid implementation-detail tests.
|
|
18
|
+
- Avoid redundant cases and brittle assertions.
|
|
19
|
+
- Do not write or edit tests.
|
|
20
|
+
- Return a concise test plan.
|
|
@@ -11,7 +11,7 @@ import util from "util";
|
|
|
11
11
|
import childProcess from "child_process";
|
|
12
12
|
//#region package.json
|
|
13
13
|
var name = "@hurshb50/setup-ubuntu";
|
|
14
|
-
var version = "2.0.
|
|
14
|
+
var version = "2.0.1";
|
|
15
15
|
//#endregion
|
|
16
16
|
//#region source/modules/logger/logger.ts
|
|
17
17
|
var Logger = class Logger {
|