Repository navigation
item-edit: reframe help around by-name editing as the first-class flow #13898
Description
Follow-up from review of #13807.
During review, @BagToad suggested that now that gh project item-edit supports name-based addressing (--owner / --number / --url / --field), the help doc could be reorganized to present editing by name as the first-class flow, with node-ID editing (--id / --field-id / --single-select-option-id) framed as a convenience for machine/scripted use.
This is a docs/UX refinement only, with no behavior change. #13807 keeps the existing structure (both paths presented in parallel); this issue tracks the potential reframe as a separate follow-up so the PR scope stays on the resolver and addressing work.
Possible scope:
- Restructure the
Longhelp so the by-name example is primary. - Present the node-ID flags as the machine-friendly alternative rather than the default.
- Consider whether the same reframe applies to related
gh projectcommands (e.g.item-list).
Context: the reframe thread on #13807.
Activity
cli-triage commentedon Jul 16, 2026
Suggesting
enhancementandgh-projectfor this issue. It's a clearly scoped docs/UX refinement — reframing thegh project item-edithelp text to present by-name editing as the primary flow — with no behavior change requested. No duplicates were found. No additional information is needed; the scope and motivation are well-described.github-actions commentedon Jul 17, 2026
Thank you for your issue! We have categorized it as an enhancement (feature or improvement) request, and it has been added to our backlog. In doing so, we are not committing to implementing this feature at this time, but, we will consider it for future releases based on community feedback and our own product roadmap.
Unless you see the help wantedContributions welcome
label, we are not currently looking for external contributions for this feature.
If you come across this issue and would like to see it implemented, please add a thumbs up! This will help us prioritize the feature. Please only comment if you have additional information or viewpoints to contribute.
feat(issues): qualify a commit closer with its repository when it is …