personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Release: labels-sync documentation improvements #69

Merged
lmiranda merged 2 commits from development into main 2026-01-21 21:16:28 +00:00
Conversation 0 Commits 2 Files Changed 1 +74 -84
lmiranda commented 2026-01-21 21:14:44 +00:00
Owner
Copy Link

Summary

Merges documentation improvements for labels-sync command.

Changes

  • Removed misleading [Y/n] prompts from documentation
  • Clarified autonomous execution behavior
  • Updated examples to reflect actual behavior
  • Improved troubleshooting section

Addresses issues 2 and 3 from #67

## Summary Merges documentation improvements for labels-sync command. ### Changes - Removed misleading `[Y/n]` prompts from documentation - Clarified autonomous execution behavior - Updated examples to reflect actual behavior - Improved troubleshooting section Addresses issues 2 and 3 from #67
lmiranda added 2 commits 2026-01-21 21:14:44 +00:00
docs: clarify labels-sync command behavior and remove misleading prompts aa3ff016e2 
Updates labels-sync.md to:
- Remove [Y/n] prompts that suggested manual confirmation
- Clarify that execution is autonomous
- Document that labels are fetched dynamically (not from reference file)
- Update examples to show actual behavior
- Improve troubleshooting for common issues
- Add user-owned repo handling documentation

Related to #67

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Merge pull request 'docs: clarify labels-sync command behavior' (#68) from docs/labels-sync-clarification into development 71efa1aafa
lmiranda merged commit b2c51251f3 into main 2026-01-21 21:16:28 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#69
Delete Branch "development"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?