### Manage GitHub Issues with GitHub CLI

Source: https://context7.com/kubevela/community/llms.txt

Commands to manage GitHub issues using the GitHub CLI, including setting labels for priority and help wanted, commenting on duplicates, and labeling issues for follow-up.

```bash
gh issue edit 123 --add-label "priority/critical"
gh issue edit 124 --add-label "priority/important-soon"
gh issue edit 125 --add-label "help wanted" --add-label "good first issue"
gh issue comment 126 --body "/duplicate of #100"
gh issue edit 127 --add-label "bot/no new info"
```

--------------------------------

### Create KubeVela Enhancement Proposal (KEP)

Source: https://context7.com/kubevela/community/llms.txt

Workflow for creating a KubeVela Enhancement Proposal (KEP). This includes forking the repository, creating a design document, submitting a pull request, and engaging in discussion.

```bash
git clone https://github.com/YOUR_USERNAME/kubevela.git
cd kubevela
mkdir -p design/vela-core
cat > design/vela-core/my-feature-proposal.md <<EOF
# KEP: My Feature Proposal

## Summary
One paragraph summary of the proposal.

## Motivation
Why is this needed? What problem does it solve?

## Proposal
Detailed design including:
- API changes
- Architecture diagrams
- Implementation phases

## Compatibility
Backward compatibility considerations.

## Alternatives
Other approaches considered and why they were rejected.
EOF
git checkout -b proposal/my-feature
git add design/vela-core/my-feature-proposal.md
git commit -m "KEP: Add proposal for my feature"
git push origin proposal/my-feature

gh pr create \
  --title "KEP: My Feature Proposal" \
  --body "This proposal introduces... [summary]

Please review and provide feedback on:
1. API design
2. Migration strategy
3. Performance implications"
```

--------------------------------

### Automate KubeVela Issue Management with Bot Commands

Source: https://context7.com/kubevela/community/llms.txt

This set of commands utilizes the 'gh' CLI to interact with GitHub issues for KubeVela project management. It covers functionalities like marking duplicates, requesting more information, applying labels for categorization (type, area, priority, effort), marking for community help, and closing invalid issues. These commands automate routine tasks for maintainers and reviewers.

```bash
# Available issue bot commands

# 1. Mark as duplicate
gh issue comment 456 --repo kubevela/kubevela --body "/duplicate #123"
# Result: Applies type/duplicate label, adds linking comment, closes issue

# 2. Mark stale issues (automatically by bot)
gh issue edit 789 --add-label "bot/no new info"
# After 14 days with no response, bot automatically closes

# 3. Request more information
gh issue comment 101 --body "Thanks for the report! To investigate further, please provide:
- KubeVela version: \`vela version\`
- Kubernetes version: \`kubectl version\`
- Application YAML that reproduces the issue
- Complete error logs"

gh issue edit 101 --add-label "needs more info"

# 4. Label by type and area
gh issue edit 202 \
  --add-label "type/bug" \
  --add-label "area/workflow" \
  --add-label "priority/important-soon"

# 5. Mark for community help
gh issue edit 303 \
  --add-label "help wanted" \
  --add-label "good first issue" \
  --add-label "effort/small"

# 6. Close invalid issues
gh issue comment 404 --body "This appears to be a usage question rather than a bug.
Please use GitHub Discussions for questions: https://github.com/kubevela/kubevela/discussions"
gh issue edit 404 --add-label "type/question" --state closed
```

--------------------------------

### Issue Triage Process - Shell and GitHub CLI

Source: https://context7.com/kubevela/community/llms.txt

This snippet demonstrates a process for triaging GitHub issues using cURL for API interaction and the GitHub CLI (`gh`) for issue management. It involves fetching unlabeled open issues and applying labels for type and functional area. Dependencies include `curl`, `jq`, and the GitHub CLI.

```bash
# Check for unlabeled issues that need triage
curl -H "Authorization: token YOUR_TOKEN" \
  "https://api.github.com/repos/kubevela/kubevela/issues?state=open&labels=" | \
  jq '.[] | {number: .number, title: .title, created: .created_at}'

# Triage workflow example
# 1. Label by type
gh issue edit 123 --add-label "type/bug"
gh issue edit 124 --add-label "type/enhancement"
gh issue edit 125 --add-label "type/docs"

# 2. Add functional area labels
gh issue edit 123 --add-label "area/core"
gh issue edit 124 --add-label "area/cli"

```

--------------------------------

### Manage KubeVela Adopter Listing

Source: https://context7.com/kubevela/community/llms.txt

This snippet demonstrates how to add an organization to the KubeVela adopters list. It involves commenting on a specific GitHub issue with organization details and then manually updating the ADOPTERS.md file. It also includes commands to view the current adopters list and analyze adoption status distribution.

```bash
# Add your organization to KubeVela adopters list

# 1. Comment on tracking issue
gh issue comment 1662 \
  --repo kubevela/kubevela \
  --body "**Organization:** Acme Corporation
**Website:** https://acme.com
**Status:** Production
**Use Case:** Multi-cloud application delivery for 200+ microservices
**Reference:** https://acme.com/blog/kubevela-adoption
**Contact:** @acme-devops-team"

# 2. Maintainers update ADOPTERS.md
# After verification, maintainers add entry:
cat >> ADOPTERS.md <<EOF
| [Acme Corporation](https://acme.com/) | ![production](https://img.shields.io/badge/-production-blue?style=flat) | [blog](https://acme.com/blog/kubevela-adoption) |
EOF

# View current adopters
curl -s https://raw.githubusercontent.com/kubevela/community/main/ADOPTERS.md \
  | 
  grep -E '[\[.*](http' | head -10

# Check adoption status distribution
curl -s https://raw.githubusercontent.com/kubevela/community/main/ADOPTERS.md \
  | 
  grep -o 'production|testing' | sort | uniq -c
```

--------------------------------

### Maintainer Step Down Process

Source: https://context7.com/kubevela/community/llms.txt

Process for a maintainer to step down from their role using the GitHub CLI by creating an issue in the kubevela repository.

```bash
gh issue create \
  --repo kubevela/kubevela \
  --title "Stepping down as maintainer: @yourname" \
  --body "Due to time constraints, I'm stepping down as maintainer effective immediately."
```

--------------------------------

### Automated Community Meeting Scheduler (English) - GitHub Actions

Source: https://context7.com/kubevela/community/llms.txt

This GitHub Actions workflow automates the creation of community meeting agenda issues for the English-speaking community. It runs on a schedule, checks for the third Thursday of the month, and creates a pinned issue with meeting details. Dependencies include the 'imjohnbo/issue-bot@v3' action.

```yaml
# .github/workflows/bot-en.yml
name: Weekly Community Call (EN)
on:
  schedule:
    - cron: 0 15 * * 3  # Every Wednesday at 3 PM UTC
  workflow_dispatch:

jobs:
  en-community-cal:
    name: Community Call Raise
    runs-on: ubuntu-latest
    steps:
      - name: Check if meeting week
        id: check_week
        run: |-
          TODAY=$(date +%Y-%m-%d)
          TOMORROW=$(date -d "+1 day" +%Y-%m-%d)

          if [ $(date +%u) -eq 3 ]; then
            if [ $(date -d "$TOMORROW" +%u) -eq 4 ]; then
              DAY_OF_MONTH=$(date -d "$TOMORROW" +%d)
              if [ $DAY_OF_MONTH -ge 15 ] && [ $DAY_OF_MONTH -le 21 ]; then
                echo "should_run=true" >> $GITHUB_OUTPUT
              fi
            fi
          fi

      - name: New Community call issue
        if: steps.check_week.outputs.should_run == 'true'
        uses: imjohnbo/issue-bot@v3
        with:
          labels: "comminity call"
          title: ${{ env.MEETINGDAY }} Community Meeting Agenda
          body: |-
            Every month on the third Thursday we host a community meeting.
            Zoom Call: https://zoom.us/j/5706981108?pwd=N0lOVit3Titwb3B2VitZbHhKU3k1Zz09
          pinned: true

```

--------------------------------

### Nominate New Maintainer

Source: https://context7.com/kubevela/community/llms.txt

Process for nominating a new maintainer using the GitHub CLI. This involves creating an issue detailing the candidate's qualifications and setting a voting period.

```bash
gh issue create \
  --repo kubevela/community \
  --title "Nomination: @candidate for Maintainer" \
  --body "I nominate @candidate for maintainer based on:
- Deep technical expertise in KubeVela core
- 50+ substantial PRs reviewed and approved
- Led design of X feature and Y enhancement
- Active for 18+ months

**Voting period:** 7 days from this issue creation"
```

--------------------------------

### Update OWNERS.md

Source: https://context7.com/kubevela/community/llms.txt

Steps to update the OWNERS.md file after a new maintainer has been approved, typically part of the maintainer addition process.

```bash
cd ../community
# Edit OWNERS.md to add new maintainer
gh pr create --title "Add @new-maintainer to maintainers" --body "Approved by 2/3 vote"
```

--------------------------------

### Automated Community Meeting Scheduler (Chinese) - GitHub Actions

Source: https://context7.com/kubevela/community/llms.txt

This GitHub Actions workflow automates the creation of community meeting agenda issues for the Chinese-speaking community. It runs bi-weekly on Tuesdays, calculating the meeting date 14 days in advance to create discussion threads. Dependencies include the 'imjohnbo/issue-bot@v3' action.

```yaml
# .github/workflows/bot-cn.yml
name: Weekly Community Call (CN)
on:
  schedule:
    - cron: 0 12 * * 2  # Every Tuesday at noon UTC

jobs:
  cn-community-cal:
    name: Community Call Raise CN
    runs-on: ubuntu-latest
    steps:
      - name: Meeting date
        run: |-
          if [ $(expr $(date +%W) % 2) -eq 0 ]; then
            echo "MEETINGDAY=$(date -d "+14 days" +"%b %d, %Y")" >> $GITHUB_ENV
            echo "MEETINGDAYNUM=$(date -d "+14 days" +"%Y%m%d")" >> $GITHUB_ENV
          else
            exit 1
          fi

      - name: New standup issue
        uses: imjohnbo/issue-bot@v3
        with:
          labels: "comminity call"
          title: ${{ env.MEETINGDAY }} Community Meeting Agenda (中文社区会议)
          body: |-
            Zoom Call: https://zoom.us/j/98479412361?pwd=MklLZGx3bkNzMlpYZ1cyZEJCdm9xUT09
            Meeting time: Tuesday ${{ env.MEETINGDAY }} 19:00 PM CST

```

--------------------------------

### Update CODEOWNERS File

Source: https://context7.com/kubevela/community/llms.txt

Steps to update the CODEOWNERS file in the kubevela repository to add a new maintainer after a successful nomination and vote.

```bash
git clone https://github.com/kubevela/kubevela.git
cd kubevela
echo "* @existing-maintainer1 @existing-maintainer2 @new-maintainer" >> .github/CODEOWNERS
git add .github/CODEOWNERS
git commit -m "Add @new-maintainer to CODEOWNERS"
git push origin main
```

--------------------------------

### Check Personal Contribution Activity

Source: https://context7.com/kubevela/community/llms.txt

Command to list pull requests authored by the current user in the kubevela repository to check activity levels.

```bash
gh pr list --author @yourname --repo kubevela/kubevela --state all --limit 10
```

--------------------------------

### Request KubeVela Organization Membership

Source: https://context7.com/kubevela/community/llms.txt

Process for requesting membership in the KubeVela GitHub organization using the GitHub CLI. This involves creating an issue with contribution details and sponsor information.

```bash
gh issue create \
  --repo kubevela/community \
  --title "Request to join KubeVela GitHub org" \
  --body "**GitHub username:** @yourname
**Contributions:**
- PR #123: Added feature X
- PR #456: Fixed bug Y
- Reviewed PRs: #789, #101

**Sponsors:** @reviewer1, @reviewer2

I've been actively contributing for 3 months and would like to become a member."
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.