issuer 0.1.0 → 0.1.1

data/specs/tests/cleanup-github-tests.sh

@@ -1,374 +0,0 @@
-#!/usr/bin/env zsh
-# GitHub Test Cleanup Script
-# Helps clean up test issues, milestones, and labels created during testing
-
-set -e
-
-# Colors for output
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-BLUE='\033[0;34m'
-NC='\033[0m' # No Color
-
-# Configuration
-TEST_REPO=""
-DRY_RUN=false
-INTERACTIVE=true
-
-print_header() {
-    echo
-    echo -e "${BLUE}===========================================${NC}"
-    echo -e "${BLUE}  🧹 GitHub Test Cleanup Script          ${NC}"
-    echo -e "${BLUE}===========================================${NC}"
-    echo
-}
-
-print_success() {
-    echo -e "${GREEN}✅ $1${NC}"
-}
-
-print_error() {
-    echo -e "${RED}❌ $1${NC}"
-}
-
-print_warning() {
-    echo -e "${YELLOW}⚠️  $1${NC}"
-}
-
-print_info() {
-    echo -e "${BLUE}ℹ️  $1${NC}"
-}
-
-show_help() {
-    echo "GitHub Test Cleanup Script"
-    echo
-    echo "Usage: $0 [options] REPOSITORY"
-    echo
-    echo "Arguments:"
-    echo "  REPOSITORY          GitHub repository (user/repo or org/repo)"
-    echo
-    echo "Options:"
-    echo "  --help, -h          Show this help message"
-    echo "  --dry-run, -n       Show what would be done without making changes"
-    echo "  --non-interactive   Run without prompts"
-    echo "  --issues-only       Only clean up issues, not milestones/labels"
-    echo "  --milestones-only   Only clean up milestones"
-    echo "  --labels-only       Only clean up labels"
-    echo
-    echo "Environment Variables:"
-    echo "  GITHUB_TOKEN        GitHub personal access token (required)"
-    echo
-    echo "Examples:"
-    echo "  $0 myuser/test-repo                    # Interactive cleanup"
-    echo "  $0 --dry-run myuser/test-repo          # Show what would be cleaned"
-    echo "  $0 --issues-only myuser/test-repo     # Only close test issues"
-    echo
-}
-
-cleanup_issues() {
-    local repo="$1"
-    
-    print_info "Searching for test issues in $repo..."
-    
-    if [[ "$DRY_RUN" == "true" ]]; then
-        print_warning "DRY RUN: Would search for and close issues with titles containing '[TEST]'"
-        echo "Command that would be run:"
-        echo "  gh issue list --repo $repo --search '[TEST]' --state open"
-        echo "  gh issue close --repo $repo [issue_numbers]"
-    else
-        # Get open test issues
-        local issue_numbers
-        issue_numbers=$(gh issue list --repo "$repo" --search '[TEST]' --state open --json number --jq '.[].number' 2>/dev/null || echo "")
-        
-        if [[ -z "$issue_numbers" ]]; then
-            print_info "No open test issues found to close"
-        else
-            print_info "Found open test issues to close:"
-            echo "$issue_numbers" | while read number; do
-                [[ -n "$number" ]] && echo "  - Issue #$number"
-            done
-            
-            if [[ "$INTERACTIVE" == "true" ]]; then
-                echo -n "Proceed with closing test issues? [y/N] "
-                read -r response
-                if [[ ! "$response" =~ ^[Yy]$ ]]; then
-                    print_info "Issue cleanup skipped by user"
-                    return
-                fi
-            fi
-            
-            print_info "Closing test issues..."
-            echo "$issue_numbers" | while read number; do
-                if [[ -n "$number" ]]; then
-                    echo "  Closing issue #$number"
-                    if gh issue close --repo "$repo" "$number" >/dev/null 2>&1; then
-                        print_success "Closed issue #$number"
-                    else
-                        print_error "Failed to close issue #$number"
-                    fi
-                fi
-            done
-        fi
-    fi
-}
-
-cleanup_milestones() {
-    local repo="$1"
-    
-    print_info "Searching for test milestones in $repo..."
-    
-    if [[ "$DRY_RUN" == "true" ]]; then
-        print_warning "DRY RUN: Would search for and delete milestones containing 'test'"
-        echo "Test milestone patterns to look for:"
-        echo "  - test-milestone-*"
-        echo "  - *-test-*"
-        echo "  - auto-test-*"
-        echo "  - complex-test-*"
-    else
-        # Get test milestones using GitHub API
-        local milestones
-        milestones=$(gh api "repos/$repo/milestones" 2>/dev/null | jq -r '.[] | select(.title | test("test|auto-test|complex-test|alias-test|individual-test")) | "\(.number) \(.title)"' 2>/dev/null || echo "")
-        
-        if [[ -z "$milestones" ]]; then
-            print_info "No test milestones found to delete"
-        else
-            print_info "Found test milestones to delete:"
-            echo "$milestones" | while read number title; do
-                [[ -n "$number" ]] && echo "  - $title (#$number)"
-            done
-            
-            if [[ "$INTERACTIVE" == "true" ]]; then
-                echo -n "Proceed with deleting test milestones? [y/N] "
-                read -r response
-                if [[ ! "$response" =~ ^[Yy]$ ]]; then
-                    print_info "Milestone cleanup skipped by user"
-                    return
-                fi
-            fi
-            
-            print_info "Deleting test milestones..."
-            echo "$milestones" | while read number title; do
-                if [[ -n "$number" && -n "$title" ]]; then
-                    echo "  Deleting milestone: $title (#$number)"
-                    if gh api -X DELETE "repos/$repo/milestones/$number" >/dev/null 2>&1; then
-                        print_success "Deleted milestone: $title"
-                    else
-                        print_error "Failed to delete milestone: $title"
-                    fi
-                fi
-            done
-        fi
-    fi
-}
-
-cleanup_labels() {
-    local repo="$1"
-    
-    print_info "Searching for test labels in $repo..."
-    
-    if [[ "$DRY_RUN" == "true" ]]; then
-        print_warning "DRY RUN: Would search for and delete labels containing 'test'"
-        echo "Test label patterns to look for:"
-        echo "  - test-*"
-        echo "  - *-test"
-        echo "  - auto-test-*"
-        echo "  - comprehensive-test"
-    else
-        # Get test labels using gh CLI
-        local labels
-        labels=$(gh label list --repo "$repo" 2>/dev/null | grep -E "(test|auto-test|brand-new|individual|alias|comprehensive)" | cut -f1 2>/dev/null || echo "")
-        
-        if [[ -z "$labels" ]]; then
-            print_info "No test labels found to delete"
-        else
-            print_info "Found test labels to delete:"
-            echo "$labels" | while read label; do
-                [[ -n "$label" ]] && echo "  - $label"
-            done
-            
-            if [[ "$INTERACTIVE" == "true" ]]; then
-                echo -n "Proceed with deleting test labels? [y/N] "
-                read -r response
-                if [[ ! "$response" =~ ^[Yy]$ ]]; then
-                    print_info "Label cleanup skipped by user"
-                    return
-                fi
-            fi
-            
-            print_info "Deleting test labels..."
-            echo "$labels" | while read label; do
-                if [[ -n "$label" ]]; then
-                    echo "  Deleting label: $label"
-                    if gh label delete --repo "$repo" "$label" --yes >/dev/null 2>&1; then
-                        print_success "Deleted label: $label"
-                    else
-                        print_error "Failed to delete label: $label"
-                    fi
-                fi
-            done
-        fi
-    fi
-}
-
-generate_cleanup_commands() {
-    local repo="$1"
-    local script_file="cleanup_commands_$(date +%Y%m%d_%H%M%S).sh"
-    
-    print_info "Generating cleanup commands script: $script_file"
-    
-    cat > "$script_file" << EOF
-#!/usr/bin/env zsh
-# Generated cleanup commands for GitHub test artifacts
-# Repository: $repo
-# Generated: $(date)
-
-set -e
-
-echo "🧹 Cleaning up test artifacts for $repo"
-echo
-
-# Close all test issues
-echo "📋 Closing test issues..."
-gh issue list --repo $repo --search '[TEST]' --state open --json number,title | \\
-  jq -r '.[] | "gh issue close --repo $repo \\(.number) # \\(.title)"' | \\
-  while read -r cmd; do
-    echo "Running: \$cmd"
-    eval "\$cmd"
-  done
-
-echo
-
-# List milestones to review (manual deletion required)
-echo "🎯 Test milestones to review:"
-gh api "repos/$repo/milestones" | jq -r '.[] | select(.title | test("test|auto-test|complex-test")) | "Milestone: \\(.title) (\\(.open_issues) open issues)"'
-
-echo
-echo "⚠️  Please manually delete test milestones from the repository web interface"
-
-echo
-
-# List labels to review (manual deletion required)  
-echo "🏷️  Test labels to review:"
-gh api "repos/$repo/labels" | jq -r '.[] | select(.name | test("test|auto-test|comprehensive-test")) | "Label: \\(.name) (\\(.description // "no description"))"'
-
-echo
-echo "⚠️  Please manually delete test labels from the repository web interface"
-
-echo
-echo "✅ Test issue cleanup completed!"
-echo "🔗 Repository: https://github.com/$repo"
-EOF
-
-    chmod +x "$script_file"
-    print_success "Cleanup script generated: $script_file"
-    print_info "Run this script to execute the cleanup commands"
-}
-
-main() {
-    local cleanup_issues=true
-    local cleanup_milestones=true
-    local cleanup_labels=true
-    
-    # Parse command line arguments
-    while [[ $# -gt 0 ]]; do
-        case $1 in
-            --help|-h)
-                show_help
-                exit 0
-                ;;
-            --dry-run|-n)
-                DRY_RUN=true
-                shift
-                ;;
-            --non-interactive)
-                INTERACTIVE=false
-                shift
-                ;;
-            --issues-only)
-                cleanup_milestones=false
-                cleanup_labels=false
-                shift
-                ;;
-            --milestones-only)
-                cleanup_issues=false
-                cleanup_labels=false
-                shift
-                ;;
-            --labels-only)
-                cleanup_issues=false
-                cleanup_milestones=false
-                shift
-                ;;
-            -*)
-                print_error "Unknown option: $1"
-                show_help
-                exit 1
-                ;;
-            *)
-                if [[ -z "$TEST_REPO" ]]; then
-                    TEST_REPO="$1"
-                else
-                    print_error "Multiple repositories specified"
-                    exit 1
-                fi
-                shift
-                ;;
-        esac
-    done
-    
-    if [[ -z "$TEST_REPO" ]]; then
-        print_error "Repository not specified"
-        show_help
-        exit 1
-    fi
-    
-    # Validate repository format
-    if [[ ! "$TEST_REPO" =~ ^[a-zA-Z0-9_.-]+/[a-zA-Z0-9_.-]+$ ]]; then
-        print_error "Invalid repository format. Use: user/repo or org/repo"
-        exit 1
-    fi
-    
-    print_header
-    
-    print_info "Repository: $TEST_REPO"
-    print_info "Dry run: $DRY_RUN"
-    print_info "Interactive: $INTERACTIVE"
-    
-    if [[ "$DRY_RUN" == "false" && "$INTERACTIVE" == "true" ]]; then
-        echo
-        echo -n "Proceed with cleanup? [y/N] "
-        read -r response
-        if [[ ! "$response" =~ ^[Yy]$ ]]; then
-            print_info "Cleanup cancelled by user"
-            exit 0
-        fi
-    fi
-    
-    echo
-    
-    # Run cleanup operations
-    if [[ "$cleanup_issues" == "true" ]]; then
-        cleanup_issues "$TEST_REPO"
-        echo
-    fi
-    
-    if [[ "$cleanup_milestones" == "true" ]]; then
-        cleanup_milestones "$TEST_REPO"
-        echo
-    fi
-    
-    if [[ "$cleanup_labels" == "true" ]]; then
-        cleanup_labels "$TEST_REPO"
-        echo
-    fi
-    
-    # Generate cleanup script if not in dry-run mode
-    if [[ "$DRY_RUN" == "false" ]]; then
-        generate_cleanup_commands "$TEST_REPO"
-    fi
-    
-    print_success "Cleanup process completed!"
-}
-
-main "$@"

data/specs/tests/github-api/01-auth-connection.yml

@@ -1,21 +0,0 @@
-$meta:
-  proj: DocOps/issuer-test  # Test repository
-  
-issues:
-  - summ: "[TEST] Authentication verification"
-    body: |
-      # Authentication Test Issue
-      
-      This issue verifies that the issuer CLI can successfully:
-      
-      - ✅ Detect GitHub authentication token
-      - ✅ Connect to GitHub API  
-      - ✅ Access the target repository
-      - ✅ Create issues via API
-      
-      **Test Details:**
-      - Created via: issuer CLI
-      - Test type: Authentication & basic connectivity
-      - Expected outcome: This issue should be created successfully
-      
-      If you can see this issue, the basic authentication and API connection is working! 🎉

data/specs/tests/github-api/02-basic-issues.yml

@@ -1,90 +0,0 @@
-$meta:
-  proj: DocOps/issuer-test  # Test repository
-  
-issues:
-  - summ: "[TEST] Simple issue creation"
-    body: |
-      # Basic Issue Test
-      
-      This tests the most fundamental functionality: creating a simple issue with a title and body.
-      
-      **What this tests:**
-      - Basic issue creation
-      - Title and body handling
-      - No additional complexity
-      
-  - summ: "[TEST] Markdown formatting support"
-    body: |
-      # Markdown Formatting Test
-      
-      This issue tests **markdown formatting** support in issue bodies.
-      
-      ## Features tested:
-      
-      ### Text formatting:
-      - **Bold text**
-      - *Italic text*
-      - `inline code`
-      - ~~strikethrough~~
-      
-      ### Lists:
-      1. Numbered list item 1
-      2. Numbered list item 2
-      
-      - Bullet point 1
-      - Bullet point 2
-        - Nested bullet
-        - Another nested bullet
-      
-      ### Code blocks:
-      ```javascript
-      function testFunction() {
-        console.log("Hello, GitHub Issues!");
-        return "markdown test";
-      }
-      ```
-      
-      ```yaml
-      # YAML example
-      test:
-        markdown: true
-        formatting: working
-      ```
-      
-      ### Links and references:
-      - [GitHub Documentation](https://docs.github.com)
-      - [issuer CLI Repository](https://github.com/DocOps/issuer)
-      
-      ### Tables:
-      | Feature | Status | Notes |
-      |---------|--------|-------|
-      | Bold text | ✅ | Working |
-      | Code blocks | ✅ | Working |
-      | Tables | ✅ | Working |
-      
-      > **Note**: This is a blockquote to test quotation formatting.
-      
-      If all the above formatting appears correctly, markdown support is working! 🎨
-      
-  - "[TEST] String-only issue (minimal syntax)"
-    
-  - summ: "[TEST] Issue with special characters"
-    body: |
-      # Special Characters Test 🚀
-      
-      Testing various special characters and emoji support:
-      
-      **Unicode characters:** αβγδε ñáéíóú 中文 日本語 العربية
-      
-      **Symbols:** @#$%^&*()_+-=[]{}|;':",./<>?
-      
-      **Emojis:** 🎉 🚀 ✅ ❌ 🔧 📋 💡 🎯 📊 🔍
-      
-      **Code with special chars:**
-      ```bash
-      echo "Testing special chars: !@#$%^&*()"
-      grep -r "pattern" /path/to/files
-      sed 's/old/new/g' file.txt
-      ```
-      
-      This tests the robustness of issue creation with various character encodings.

data/specs/tests/github-api/03-milestone-tests.yml

@@ -1,58 +0,0 @@
-$meta:
-  proj: DocOps/issuer-test  # Test repository
-  defaults:
-    vrsn: test-milestone-v1.0
-    
-issues:
-  - summ: "[TEST] Issue with new milestone creation"
-    body: |
-      # Milestone Creation Test
-      
-      This issue tests automatic milestone creation functionality.
-      
-      **What this tests:**
-      - Creating a new milestone when it doesn't exist
-      - Associating an issue with a newly created milestone
-      - The `--auto-versions` or `--auto-metadata` flag functionality
-      
-      **Expected behavior:**
-      1. A new milestone called "test-milestone-v1.0" should be created
-      2. This issue should be associated with that milestone
-      3. The milestone should appear in the repository's Milestones section
-      
-      **Test commands:**
-      ```bash
-      # With manual confirmation
-      issuer 03-milestone-tests.yml
-      
-      # With automatic creation (no prompts)
-      issuer 03-milestone-tests.yml --auto-versions
-      issuer 03-milestone-tests.yml --auto-metadata
-      ```
-      
-  - summ: "[TEST] Issue with existing milestone"
-    body: |
-      # Existing Milestone Test
-      
-      This issue should use the same milestone as the previous issue, testing that:
-      
-      - The CLI can find and reuse existing milestones
-      - Multiple issues can be assigned to the same milestone
-      - No duplicate milestones are created
-      
-      This issue should be associated with the "test-milestone-v1.0" milestone.
-    vrsn: test-milestone-v1.0
-    
-  - summ: "[TEST] Issue with different milestone"
-    body: |
-      # Multiple Milestone Test
-      
-      This issue tests creating and using a second milestone.
-      
-      **Expected behavior:**
-      - A new milestone "test-milestone-v2.0" should be created
-      - This issue should be associated with the new milestone
-      - Both milestones should exist in the repository
-      
-      This tests the ability to handle multiple milestones in a single operation.
-    vrsn: test-milestone-v2.0

data/specs/tests/github-api/04-label-tests.yml

@@ -1,98 +0,0 @@
-$meta:
-  proj: DocOps/issuer-test  # Test repository
-  defaults:
-    tags: [test-default-label, +auto-applied-label]
-    
-issues:
-  - summ: "[TEST] Issue with new label creation"
-    body: |
-      # Label Creation Test
-      
-      This issue tests automatic label creation functionality.
-      
-      **What this tests:**
-      - Creating new labels when they don't exist
-      - The `--auto-tags` or `--auto-metadata` flag functionality
-      - Default label application from `$meta.defaults.tags`
-      
-      **Expected labels on this issue:**
-      - `test-new-label-1` (new, should be created)
-      - `test-new-label-2` (new, should be created)  
-      - `test-default-label` (from defaults)
-      - `auto-applied-label` (from defaults with + prefix)
-      
-      **Test commands:**
-      ```bash
-      # With manual confirmation
-      issuer 04-label-tests.yml
-      
-      # With automatic creation (no prompts)
-      issuer 04-label-tests.yml --auto-tags
-      issuer 04-label-tests.yml --auto-metadata
-      ```
-    tags: [test-new-label-1, test-new-label-2]
-    
-  - summ: "[TEST] Issue with mixed existing/new labels"
-    body: |
-      # Mixed Label Test
-      
-      This issue tests using a combination of:
-      - Existing labels that are already in the repository
-      - New labels that need to be created
-      - Default labels from metadata
-      
-      **Expected labels on this issue:**
-      - `bug` (should already exist in most repositories)
-      - `enhancement` (should already exist in most repositories)
-      - `test-mixed-new-label` (new, should be created)
-      - `test-default-label` (from defaults)
-      - `auto-applied-label` (from defaults with + prefix)
-      
-      This tests the CLI's ability to handle mixed scenarios gracefully.
-    tags: [bug, enhancement, test-mixed-new-label]
-    
-  - summ: "[TEST] Issue with label append vs. default behavior"
-    body: |
-      # Label Logic Test
-      
-      This issue has its own explicit tags, so it should:
-      
-      **Get these labels:**
-      - `test-explicit-label-1` (explicitly specified)
-      - `test-explicit-label-2` (explicitly specified)
-      - `auto-applied-label` (from defaults with + prefix - always appended)
-      
-      **NOT get these labels:**
-      - `test-default-label` (from defaults without + prefix - only for issues without explicit tags)
-      
-      This tests the append (+) vs. default tag logic.
-    tags: [test-explicit-label-1, test-explicit-label-2]
-    
-  - summ: "[TEST] Issue with no explicit tags (should get defaults)"
-    body: |
-      # Default Label Test
-      
-      This issue has no explicit tags, so it should get all default labels:
-      
-      **Expected labels:**
-      - `test-default-label` (from defaults without + prefix)
-      - `auto-applied-label` (from defaults with + prefix)
-      
-      This tests that default labels are properly applied to issues without explicit tags.
-      
-  - summ: "[TEST] Label color and description test"
-    body: |
-      # Label Customization Test
-      
-      This issue tests whether custom label colors and descriptions are supported.
-      
-      **Note:** The current implementation may create labels with default colors.
-      Future versions might support custom colors and descriptions in the IMYML format.
-      
-      **Expected labels:**
-      - `test-color-label` (new label)
-      - `test-description-label` (new label)
-      - Default labels from metadata
-      
-      Check the repository's Labels section to see what colors were assigned to the new labels.
-    tags: [test-color-label, test-description-label]

data/specs/tests/github-api/05-assignment-tests.yml

@@ -1,55 +0,0 @@
-$meta:
-  proj: DocOps/issuer-test              # Test repository  # Update this with your test repository
-  
-issues:
-  - summ: "[TEST] Self-assigned issue"
-    body: |
-      # Assignment Test
-      
-      This issue tests the user assignment functionality.
-      
-      **What this tests:**
-      - Assigning an issue to a specific user
-      - User validation (the user must have access to the repository)
-      - Assignment display in the GitHub interface
-      
-      **Expected behavior:**
-      - This issue should be assigned to the repository owner/collaborator
-      - The assignee should appear in the GitHub Issues interface
-      - The assignee should receive notifications (if configured)
-      
-      **Important:** Make sure to update the `user` field below with a valid GitHub username that has access to the test repository.
-      
-      **Test commands:**
-      ```bash
-      issuer 05-assignment-tests.yml --dry  # Check assignment before posting
-      issuer 05-assignment-tests.yml        # Create with assignment
-      ```
-    user: briandominick               # GitHub username  # Update this with a valid GitHub username
-    
-  - summ: "[TEST] Issue with default assignee"
-    body: |
-      # Default Assignee Test
-      
-      This issue tests using a default assignee specified in metadata defaults.
-      
-      **Expected behavior:**
-      - Should be assigned to the same user as specified in defaults
-      - Tests the inheritance of user assignment from metadata
-      
-      Note: This test requires setting a default user in the metadata section.
-    # This issue will use the default user from $meta.defaults if specified
-    
-  - summ: "[TEST] Unassigned issue"
-    body: |
-      # Unassigned Issue Test
-      
-      This issue should remain unassigned to test that:
-      
-      - Issues without explicit or default assignees work correctly
-      - The assignment field is properly omitted from the API call
-      - No errors occur when no assignee is specified
-      
-      **Expected behavior:**
-      - This issue should appear with no assignee in GitHub
-      - No assignment-related errors should occur during creation