# 2ticketss
2 complementary command-line tools for GitHub issue management - **00-jira-to-gh-issues**: A Rust tool that converts Jira CSV exports to GitHub issue markdown files compatible with gh-issue-generator. It handles messy CSV data and preserves issue metadata - **01-gh-issue-generator**: A Rust tool that creates GitHub issues from Markdown files with YAML front matter. It parses structured Markdown, supports batch processing, and integrates with GitHub CLI
This commit is contained in:
127
01-gh-issue-generator/examples/batch.md
Normal file
127
01-gh-issue-generator/examples/batch.md
Normal file
@@ -0,0 +1,127 @@
|
||||
# Batch Issues Example
|
||||
|
||||
This file demonstrates how to use our tool with a single batch file containing multiple issues.
|
||||
To use this approach, save this as a markdown file and run:
|
||||
|
||||
```
|
||||
gh-issue-generator --repo owner/repo batch.md
|
||||
```
|
||||
|
||||
Note: Each issue must be separated by the delimiter `---ISSUE---`
|
||||
|
||||
---ISSUE---
|
||||
|
||||
---
|
||||
title: Implement user registration flow
|
||||
status: ready
|
||||
labels:
|
||||
- feature
|
||||
- frontend
|
||||
- backend
|
||||
assignees:
|
||||
- frontend-dev
|
||||
- backend-dev
|
||||
milestone: v1.0
|
||||
project: User Management
|
||||
---
|
||||
|
||||
## Description
|
||||
|
||||
Create a complete user registration flow including email verification.
|
||||
|
||||
## Requirements
|
||||
|
||||
- Registration form with validation
|
||||
- Email verification process
|
||||
- Welcome email
|
||||
- Database schema updates
|
||||
|
||||
## Tasks
|
||||
|
||||
- [ ] Design registration form
|
||||
- [ ] Implement frontend validation
|
||||
- [ ] Create backend API endpoints
|
||||
- [ ] Set up email verification system
|
||||
- [ ] Update user database schema
|
||||
- [ ] Add welcome email template
|
||||
|
||||
---ISSUE---
|
||||
|
||||
---
|
||||
title: Add product search functionality
|
||||
status: ready
|
||||
labels:
|
||||
- feature
|
||||
- search
|
||||
milestone: v1.0
|
||||
project: Product Catalog
|
||||
---
|
||||
|
||||
## Description
|
||||
|
||||
Implement search functionality for the product catalog.
|
||||
|
||||
## Requirements
|
||||
|
||||
- Search by product name, description, and tags
|
||||
- Autocomplete suggestions
|
||||
- Filter by category and price range
|
||||
- Sort results by relevance, price, or rating
|
||||
|
||||
## Technical Approach
|
||||
|
||||
Use Elasticsearch for the search index and implement a React component for the frontend.
|
||||
|
||||
---ISSUE---
|
||||
|
||||
---
|
||||
title: Optimize image loading performance
|
||||
status: draft
|
||||
labels:
|
||||
- performance
|
||||
- frontend
|
||||
---
|
||||
|
||||
## Description
|
||||
|
||||
Optimize image loading to improve page performance and Core Web Vitals metrics.
|
||||
|
||||
## Ideas to Consider
|
||||
|
||||
- Implement lazy loading for images
|
||||
- Use responsive images with srcset
|
||||
- Add image compression pipeline
|
||||
- Consider using a CDN for image delivery
|
||||
|
||||
This is currently in draft because we need to gather performance metrics first.
|
||||
|
||||
---ISSUE---
|
||||
|
||||
---
|
||||
title: Update third-party dependencies
|
||||
status: ready
|
||||
labels:
|
||||
- maintenance
|
||||
- security
|
||||
assignees:
|
||||
- devops-team
|
||||
---
|
||||
|
||||
## Description
|
||||
|
||||
Update all third-party dependencies to their latest versions to address security vulnerabilities.
|
||||
|
||||
## Dependencies to Update
|
||||
|
||||
- React and related packages
|
||||
- Backend frameworks
|
||||
- Database drivers
|
||||
- Testing libraries
|
||||
|
||||
## Steps
|
||||
|
||||
1. Review current dependencies
|
||||
2. Check for security advisories
|
||||
3. Create upgrade plan
|
||||
4. Test upgrades in staging
|
||||
5. Deploy to production
|
||||
Reference in New Issue
Block a user