From d2da35df216eef03611b5020e6ea0c2917c16f81 Mon Sep 17 00:00:00 2001 From: ROSHAN KUMAR SAH Date: Fri, 21 Nov 2025 00:44:01 +0530 Subject: [PATCH] Delete .github directory --- .github/ISSUE_TEMPLATE/bug_report.yml | 48 ------------------- .github/ISSUE_TEMPLATE/feature_request.yml | 33 ------------- .github/workflows/close-invalid.yml | 36 -------------- .../workflows/close-single-word-issues.yml | 44 ----------------- .github/workflows/feature-request-comment.yml | 31 ------------ .github/workflows/no-response.yml | 34 ------------- .github/workflows/on-issue-close.yml | 17 ------- .github/workflows/remove-triage-label.yml | 22 --------- .github/workflows/stale-issues.yml | 20 -------- .github/workflows/triage-issues.yml | 34 ------------- .../workflows/unable-to-reproduce-comment.yml | 46 ------------------ 11 files changed, 365 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 .github/workflows/close-invalid.yml delete mode 100644 .github/workflows/close-single-word-issues.yml delete mode 100644 .github/workflows/feature-request-comment.yml delete mode 100644 .github/workflows/no-response.yml delete mode 100644 .github/workflows/on-issue-close.yml delete mode 100644 .github/workflows/remove-triage-label.yml delete mode 100644 .github/workflows/stale-issues.yml delete mode 100644 .github/workflows/triage-issues.yml delete mode 100644 .github/workflows/unable-to-reproduce-comment.yml diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index f488ac30..00000000 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,48 +0,0 @@ -name: 🐞 Bug Report -description: Report a bug or unexpected behavior in the GitHub Copilot CLI. -type: Bug -labels: - - "triage" -body: - - type: markdown - attributes: - value: | -
- Thank you for taking the time to report a bug! Please answer each question below to the best of your ability; it is okay to leave questions blank if you have to. - - type: textarea - id: description - attributes: - label: Describe the bug - description: A clear and concise description of what the bug is. - - type: input - id: version - attributes: - label: Affected version - description: The version of the `copilot` where you encountered the bug (if applicable). - placeholder: | - Paste output from `copilot --version` - - type: textarea - id: steps_to_reproduce - attributes: - label: Steps to reproduce the behavior - description: A clear and concise list of steps to reproduce the behavior. Please include any commands you ran and their output. - placeholder: | - 1. Type '...' - 2. View the output '...' - 3. See error - - type: textarea - id: expected_behavior - attributes: - label: Expected behavior - description: A clear and concise description of what you expected to happen. - - type: textarea - id: additional_context - attributes: - label: Additional context - description: Add any other context about the problem here. - placeholder: | - - Logs using `--log-level` and `--log-file` flags - - Operating system (e.g., Windows, macOS, Linux) - - CPU architecture (e.g., x86_64, ARM) - - Terminal emulator (e.g., Terminal, iTerm2, Windows Terminal) - - Shell (e.g., bash, zsh, fish) diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 0a31afd7..00000000 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,33 +0,0 @@ -name: ⭐️ Feature Request -description: Suggest a new feature or improvement for the GitHub Copilot CLI. -type: Feature -labels: - - "triage" -body: - - type: markdown - attributes: - value: | -
- Thank you for taking the time to suggest a feature! Please answer each question below to the best of your ability; it is okay to leave questions blank if you have to. - - type: input - id: title - attributes: - label: Describe the feature or problem you'd like to solve - description: A clear and concise description of what the feature or problem is. - - type: textarea - id: description - attributes: - label: Proposed solution - description: How will it benefit GitHub Copilot CLI and its users? - - type: textarea - id: examples - attributes: - label: Example prompts or workflows - description: Share 3-5 example prompts or workflows it would enable; just enough detail to show value. - - type: textarea - id: additional_context - attributes: - label: Additional context - description: Add any other context about the feature request here. - placeholder: | - - Screenshots or mockups diff --git a/.github/workflows/close-invalid.yml b/.github/workflows/close-invalid.yml deleted file mode 100644 index 4078bd87..00000000 --- a/.github/workflows/close-invalid.yml +++ /dev/null @@ -1,36 +0,0 @@ -name: Close issue/PR on adding invalid label - -# **What it does**: This action closes issues that are labeled as invalid in the repo. - -on: - issues: - types: [labeled] - pull_request_target: - types: [labeled] - -permissions: - contents: read - issues: write - pull-requests: write - -jobs: - close-on-adding-invalid-label: - if: - github.repository == 'github/copilot-cli' && github.event.label.name == - 'invalid' - runs-on: ubuntu-latest - - steps: - - name: Close issue - if: ${{ github.event_name == 'issues' }} - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - URL: ${{ github.event.issue.html_url }} - run: gh issue close $URL - - - name: Close PR - if: ${{ github.event_name == 'pull_request_target' }} - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - URL: ${{ github.event.pull_request.html_url }} - run: gh pr close $URL diff --git a/.github/workflows/close-single-word-issues.yml b/.github/workflows/close-single-word-issues.yml deleted file mode 100644 index f2ef0dae..00000000 --- a/.github/workflows/close-single-word-issues.yml +++ /dev/null @@ -1,44 +0,0 @@ -name: Close Single-Word Issues - -on: - issues: - types: - - opened - -permissions: - issues: write - -jobs: - close-issue: - runs-on: ubuntu-latest - - steps: - - name: Close Single-Word Issue - uses: actions/github-script@v7 - with: - github-token: ${{ secrets.GITHUB_TOKEN }} - script: | - const issueTitle = context.payload.issue.title.trim(); - const isSingleWord = /^\S+$/.test(issueTitle); - - if (isSingleWord) { - const issueNumber = context.payload.issue.number; - const repo = context.repo.repo; - - // Close the issue and add the invalid label - github.rest.issues.update({ - owner: context.repo.owner, - repo: repo, - issue_number: issueNumber, - labels: ['invalid'], - state: 'closed' - }); - - // Comment on the issue - await github.rest.issues.createComment({ - owner: context.repo.owner, - repo: repo, - issue_number: issueNumber, - body: `This issue may have been opened accidentally. I'm going to close it now, but feel free to open a new issue with a more descriptive title.` - }); - } diff --git a/.github/workflows/feature-request-comment.yml b/.github/workflows/feature-request-comment.yml deleted file mode 100644 index f347eb6d..00000000 --- a/.github/workflows/feature-request-comment.yml +++ /dev/null @@ -1,31 +0,0 @@ -name: Add enhancement comment -on: - issues: - types: - - labeled - -permissions: - issues: write - -jobs: - add-comment-to-enhancement-issues: - if: github.event.label.name == 'enhancement' - runs-on: ubuntu-latest - env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} - GH_REPO: ${{ github.repository }} - NUMBER: ${{ github.event.issue.number }} - BODY: > - Thank you for your issue! We have categorized it as an enhancement, - 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. - - - **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. - steps: - - run: gh issue comment "$NUMBER" --body "$BODY" diff --git a/.github/workflows/no-response.yml b/.github/workflows/no-response.yml deleted file mode 100644 index 2a864ddd..00000000 --- a/.github/workflows/no-response.yml +++ /dev/null @@ -1,34 +0,0 @@ -name: No Response - -# Automatically close issues labeled 'more-info-needed' after 7 days of inactivity -on: - schedule: - # Schedule for five minutes after the hour, every hour - - cron: '5 * * * *' - -permissions: - issues: write - -jobs: - noResponse: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v9 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - only-issue-labels: 'more-info-needed' - days-before-issue-stale: -1 # Skip stale state, go directly to close - days-before-issue-close: 7 # Close after 7 days of inactivity - days-before-pr-stale: -1 # Don't process PRs - days-before-pr-close: -1 # Don't process PRs - remove-stale-when-updated: true - close-issue-message: > - Thank you for your issue! - - We haven't gotten a response to our questions above. With only the - information that is currently in the issue, we don't have enough - information to take action. We're going to close this but don't - hesitate to reach out if you have or find the answers we need. If - you answer our questions above, this issue will automatically - reopen. - close-issue-reason: 'not_planned' diff --git a/.github/workflows/on-issue-close.yml b/.github/workflows/on-issue-close.yml deleted file mode 100644 index e768226d..00000000 --- a/.github/workflows/on-issue-close.yml +++ /dev/null @@ -1,17 +0,0 @@ -name: Remove triage tab from closed issues -on: - issues: - types: - - closed -jobs: - label_issues: - runs-on: ubuntu-latest - permissions: - issues: write - steps: - - run: gh issue edit "$NUMBER" --remove-label "$LABELS" - env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} - GH_REPO: ${{ github.repository }} - NUMBER: ${{ github.event.issue.number }} - LABELS: triage diff --git a/.github/workflows/remove-triage-label.yml b/.github/workflows/remove-triage-label.yml deleted file mode 100644 index b4834e05..00000000 --- a/.github/workflows/remove-triage-label.yml +++ /dev/null @@ -1,22 +0,0 @@ -name: Remove triage label -on: - issues: - types: - - labeled - -permissions: - issues: write - -jobs: - remove-triage-label-from-issues: - if: - github.event.label.name != 'triage' && github.event.label.name != - 'more-info-needed' - runs-on: ubuntu-latest - steps: - - run: gh issue edit "$NUMBER" --remove-label "$LABELS" - env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} - GH_REPO: ${{ github.repository }} - NUMBER: ${{ github.event.issue.number }} - LABELS: triage diff --git a/.github/workflows/stale-issues.yml b/.github/workflows/stale-issues.yml deleted file mode 100644 index 3ec537c4..00000000 --- a/.github/workflows/stale-issues.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Marks stale issues and PRs' -on: - schedule: - - cron: '30 1 * * *' # 1:30 AM UTC - -permissions: - issues: write - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v9 - with: - stale-issue-label: 'stale, triage' # The label that will be added to the issues when automatically marked as stale - start-date: '2025-01-01T00:00:00Z' # Skip stale action for issues created before it - days-before-stale: 365 - days-before-close: -1 # If -1, the issues nor pull requests will never be closed automatically. - days-before-pr-stale: -1 # If -1, no pull requests will be marked as stale automatically. - exempt-issue-labels: 'never-stale, help wanted' # issues labeled as such will be excluded them from being marked as stale diff --git a/.github/workflows/triage-issues.yml b/.github/workflows/triage-issues.yml deleted file mode 100644 index f73bb297..00000000 --- a/.github/workflows/triage-issues.yml +++ /dev/null @@ -1,34 +0,0 @@ -name: Label incoming issues -on: - issues: - types: - - reopened - - opened - - unlabeled - -permissions: - issues: write - -jobs: - label_incoming_issues: - runs-on: ubuntu-latest - if: github.event.action == 'opened' || github.event.action == 'reopened' - steps: - - run: gh issue edit "$NUMBER" --add-label "$LABELS" - env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} - GH_REPO: ${{ github.repository }} - NUMBER: ${{ github.event.issue.number }} - LABELS: triage - label_more_info_issues: - if: - github.event.action == 'unlabeled' && github.event.label.name == - 'more-info-needed' - runs-on: ubuntu-latest - steps: - - run: gh issue edit "$NUMBER" --add-label "$LABELS" - env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} - GH_REPO: ${{ github.repository }} - NUMBER: ${{ github.event.issue.number }} - LABELS: triage diff --git a/.github/workflows/unable-to-reproduce-comment.yml b/.github/workflows/unable-to-reproduce-comment.yml deleted file mode 100644 index 195739a3..00000000 --- a/.github/workflows/unable-to-reproduce-comment.yml +++ /dev/null @@ -1,46 +0,0 @@ -name: Add unable-to-reproduce comment -on: - issues: - types: - - labeled - -permissions: - issues: write - -jobs: - add-comment-to-unable-to-reproduce-issues: - if: github.event.label.name == 'unable-to-reproduce' - runs-on: ubuntu-latest - steps: - - name: Update issue - env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} - GH_REPO: ${{ github.repository }} - NUMBER: ${{ github.event.issue.number }} - LABELS: more-info-needed - BODY: > - Thank you for your issue! Unfortunately, we are unable to reproduce the - issue you are experiencing. Please provide more information so we can - help you. - - - Here are some tips for writing reproduction steps: - - Step by step instructions accompanied by screenshots or screencasts - are the best. - - Be as specific as possible; include as much detail as you can. - - If not already provided, include: - - the version of Copilot CLI you are using. - - the operating system you are using - - any environment factors you can think of. - - any custom configuration you are using. - - a log file from the day you experienced the issue (find log - files via `~/.copilot/logs`. - - If relevant and can be shared, provide the repository or code you - are using. - - If relevant and can be shared, provide the session files (find session files via `~/.copilot/history-session-state`). - - Note: This is a public repository. Please do not include any sensitive or - private information in your issue. - run: | - gh issue edit "$NUMBER" --add-label "$LABELS" - gh issue comment "$NUMBER" --body "$BODY"