@craftsamo/github-tools 0.6.0 → 0.7.0
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/.antigravity-plugin/plugin.json +1 -1
- package/.claude-plugin/plugin.json +1 -1
- package/README.md +6 -1
- package/dist/cli.js +315 -122
- package/dist/mcp.js +316 -123
- package/dist/opencode.js +315 -122
- package/package.json +1 -1
- package/plugin.json +1 -1
- package/plugin.yaml +1 -1
- package/skills/github-projects/SKILL.md +26 -4
package/README.md
CHANGED
|
@@ -217,7 +217,12 @@ none is given), and found among the boards linked to the repository, then its
|
|
|
217
217
|
organization's, then the viewer's. The token needs the `project` scope
|
|
218
218
|
(`gh auth refresh -s project`). No API sets a roadmap view's date fields, so
|
|
219
219
|
after `github_project_create` set the Roadmap view's "Date fields" to Start and
|
|
220
|
-
Target in the web UI.
|
|
220
|
+
Target in the web UI. A column that mirrors an organization's issue field is
|
|
221
|
+
read like any other, but its value is the issue's own: the board tools refuse
|
|
222
|
+
to set or clear it, and `github_issue_edit` does both.
|
|
223
|
+
`github_project_field_ensure` with `issue_field: true` adds such a column, and
|
|
224
|
+
`github_project_create` with `dates: "issue_fields"` uses the issue fields Start
|
|
225
|
+
date and Target date as an organization board's dates.
|
|
221
226
|
|
|
222
227
|
## Reads and writes
|
|
223
228
|
|