From 79c2666397c2c01fea5258c83a0ad6f19bd39dcf Mon Sep 17 00:00:00 2001 From: Sumit Sarabhai Date: Thu, 12 Feb 2026 23:51:27 +0530 Subject: [PATCH 1/3] Add auto acknowledgment workflow for new issues This workflow automatically acknowledges newly opened GitHub issues if no maintainer has already responded, ensuring timely communication with users. --- .github/workflows/issue-acknowledge.yml | 49 +++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 .github/workflows/issue-acknowledge.yml diff --git a/.github/workflows/issue-acknowledge.yml b/.github/workflows/issue-acknowledge.yml new file mode 100644 index 000000000..38e906b6d --- /dev/null +++ b/.github/workflows/issue-acknowledge.yml @@ -0,0 +1,49 @@ +name: Auto Acknowledge GH Issues + +on: + issues: + types: [opened] + +jobs: + acknowledge: + runs-on: ubuntu-latest + steps: + # Step 1: Wait 15 minutes + - name: Wait 15 minutes + run: sleep 10 + + # Step 2: Check if a maintainer already responded + - name: Check for existing maintainer response + id: check + uses: actions/github-script@v7 + with: + github-token: ${{ secrets.GITHUB_TOKEN }} + script: | + const maintainers = ['sumitmsft','dlevy-msft-sql']; + + const comments = await github.rest.issues.listComments({ + owner: context.repo.owner, + repo: context.repo.repo, + issue_number: context.payload.issue.number + }); + + const maintainerReplied = comments.data.some( + comment => maintainers.includes(comment.user.login) + ); + + core.setOutput('skip', maintainerReplied.toString()); + console.log(`Maintainer already replied: ${maintainerReplied}`); + + # Step 3: Post acknowledgement ONLY if no maintainer has responded + - name: Post acknowledgement comment + if: steps.check.outputs.skip == 'false' + uses: actions/github-script@v7 + with: + github-token: ${{ secrets.SUMIT_PAT_FOR_AUTO_RESPONSE }} + script: | + await github.rest.issues.createComment({ + owner: context.repo.owner, + repo: context.repo.repo, + issue_number: context.payload.issue.number, + body: `Hi @${context.payload.issue.user.login}, thank you for opening this issue!\n\nOur team will review it shortly. We aim to triage all new issues within 24-48 hours and get back to you.\n\nThank you for your patience!` + }); From 73e5bbfb0a48d78748ab3f87a8f72c273e88cecc Mon Sep 17 00:00:00 2001 From: Sumit Sarabhai Date: Fri, 13 Feb 2026 15:10:33 +0530 Subject: [PATCH 2/3] Potential fix for code scanning alert no. 747: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> --- .github/workflows/issue-acknowledge.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/issue-acknowledge.yml b/.github/workflows/issue-acknowledge.yml index 38e906b6d..cad03f52b 100644 --- a/.github/workflows/issue-acknowledge.yml +++ b/.github/workflows/issue-acknowledge.yml @@ -7,6 +7,8 @@ on: jobs: acknowledge: runs-on: ubuntu-latest + permissions: + issues: read steps: # Step 1: Wait 15 minutes - name: Wait 15 minutes From 9cb294628bc12a265cc598b4c0f988548885ac85 Mon Sep 17 00:00:00 2001 From: Sumit Sarabhai Date: Fri, 13 Feb 2026 15:10:50 +0530 Subject: [PATCH 3/3] Update .github/workflows/issue-acknowledge.yml Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .github/workflows/issue-acknowledge.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/issue-acknowledge.yml b/.github/workflows/issue-acknowledge.yml index cad03f52b..f35f22414 100644 --- a/.github/workflows/issue-acknowledge.yml +++ b/.github/workflows/issue-acknowledge.yml @@ -4,6 +4,9 @@ on: issues: types: [opened] +permissions: + contents: read + issues: write jobs: acknowledge: runs-on: ubuntu-latest