Skip to content

feat(csat): Add CSAT survey workflow#1

Merged
rshashank17 merged 1 commit into
mainfrom
shashank_csat
May 8, 2026
Merged

feat(csat): Add CSAT survey workflow#1
rshashank17 merged 1 commit into
mainfrom
shashank_csat

Conversation

@rshashank17
Copy link
Copy Markdown
Owner

Problem:

The repository currently lacks an automated mechanism to collect user feedback (Customer Satisfaction survey) when issues are resolved and closed.

Solution:

This PR implements a Customer Satisfaction (CSAT) survey workflow for the ADK Python repository. When an issue is closed, a GitHub Actions workflow is triggered to post a comment with a survey link if the issue has specific relevant labels.

Changes:

  • .github/workflows/csat.yml: Workflow definition file that triggers on issues: closed and runs the script.
  • .github/scripts/csat.js: JavaScript script that checks issue labels and posts the CSAT comment with generated links.
  • .github/scripts/constant.js: Constants file containing labels, base URL, and message strings for the survey.

Labels Checked:

The script will post the survey if the closed issue contains any of the following labels:

  • bug
  • core
  • tools
  • services
  • models
  • mcp
  • auth
  • live
  • documentation
  • good first issue
  • agent engine
  • bq
  • eval
  • tracing
  • web
  • workflow
  • request clarification
  • needs review

Testing Plan

Manual End-to-End (E2E) Tests:

  1. Label an issue in the ADK Python repository with one of the supported labels listed above.
  2. Close the issue.
  3. Verify that the GitHub Action triggers and posts the CSAT survey comment with the correct links.

Checklist

  • I have read the CONTRIBUTING.md document.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have manually tested my changes end-to-end.

Additional context

The survey links to a Google Form with pre-filled parameters for the issue URL and satisfaction level (Yes/No).

@rshashank17 rshashank17 merged commit 685239e into main May 8, 2026
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant