@arjunkhera/atlas 0.3.20 → 0.3.21
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/package.json
CHANGED
package/skills/feedback/SKILL.md
CHANGED
|
@@ -29,7 +29,25 @@ goes to the `atlas:learnings` skill instead.
|
|
|
29
29
|
6. **Show the draft, and wait.** File nothing until the person says
|
|
30
30
|
"file it", or the same in their own words.
|
|
31
31
|
7. **File it once.** Use `gh issue create --repo <repo> --title <title>
|
|
32
|
-
--body-file <file>`.
|
|
32
|
+
--body-file <file>`.
|
|
33
|
+
8. **Put the issue in the tracker.** Every open issue has a tracker item.
|
|
34
|
+
The lead does this step, because only the lead writes to the tracker.
|
|
35
|
+
1. Call `item_propose` with the product and the repo of the issue.
|
|
36
|
+
Use the issue title as the title. Use the person's own words as
|
|
37
|
+
the origin, with the issue link as its source.
|
|
38
|
+
2. Call `item_link` on the new item with kind `issue`, the issue URL
|
|
39
|
+
and role `report`.
|
|
40
|
+
3. Add a comment on the issue that names the item id.
|
|
41
|
+
4. Give the person the issue link and the item id.
|
|
42
|
+
|
|
43
|
+
If the issue adds to an open issue that has an item, link it to that
|
|
44
|
+
item instead, and make no new item. If `item_propose` refuses because
|
|
45
|
+
the owner is not present, give the person the issue link and say that
|
|
46
|
+
the owner must add the item.
|
|
47
|
+
|
|
48
|
+
Example: the person says "Atlas should show which copy runs", then
|
|
49
|
+
"file it". The lead files issue #150, proposes the item "Show which copy
|
|
50
|
+
of Atlas runs", links #150 to it, and comments the item id on #150.
|
|
33
51
|
|
|
34
52
|
When `gh` fails or is not there, use the session's GitHub tools for the
|
|
35
53
|
same search and the same issue.
|
|
@@ -40,3 +58,5 @@ same search and the same issue.
|
|
|
40
58
|
2. Never put a private name, a path on someone's machine, a secret or an
|
|
41
59
|
email address in an issue.
|
|
42
60
|
3. One report is one issue. Split a report that holds two asks.
|
|
61
|
+
4. Never leave a filed issue with no tracker item, except when the owner
|
|
62
|
+
is not present. Then say so.
|