Skip to content

feat: Implement CSAT survey workflow for ADK-Java#1188

Open
rshashank17 wants to merge 1 commit into
google:mainfrom
rshashank17:shashank_csat
Open

feat: Implement CSAT survey workflow for ADK-Java#1188
rshashank17 wants to merge 1 commit into
google:mainfrom
rshashank17:shashank_csat

Conversation

@rshashank17

Copy link
Copy Markdown

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 Java 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
  • documentation
  • good first issue
  • enhancement
  • question
  • java
  • sample
  • testing
  • contrib
  • dependencies
  • duplicate
  • github
  • needs update
  • ready to pull

Testing Plan

Manual End-to-End (E2E) Tests:

  1. Label an issue in the ADK Java 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).

@hemasekhar-p hemasekhar-p self-assigned this Jul 10, 2026
@hemasekhar-p

Copy link
Copy Markdown
Contributor

Hi @rshashank17, thank you for your contribution! We appreciate you taking the time to submit this pull request. As per contribution policy, please ensure your PR consists of a single commit. Could you please change your commits accordingly?

@hemasekhar-p hemasekhar-p added the waiting on reporter Waiting for reaction by reporter. Failing that, maintainers will eventually closed it as stale. label Jul 10, 2026
@rshashank17

Copy link
Copy Markdown
Author

Hi @hemasekhar-p ,

Done! The commits have been squashed into a single commit and the workflow file has been updated for Zizmor security compliance.

@hemasekhar-p

Copy link
Copy Markdown
Contributor

thank you for quick response @rshashank17, Currently this PR is under review by our team, we will keep you posted if any additional information is required. thank you.

@hemasekhar-p hemasekhar-p added needs review and removed waiting on reporter Waiting for reaction by reporter. Failing that, maintainers will eventually closed it as stale. labels Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants