Explore testing strategy for new features#20
Merged
Jython1415 merged 3 commits intomainfrom Jan 17, 2026
Merged
Conversation
Documents the recommended workflow for testing new features before rolling them out to users. The strategy uses feature branches with local clasp push for validation before merging to main and auto-deploying to production.
Jython1415
commented
Jan 17, 2026
Comment on lines
43
to
72
| ## Testing New Features | ||
|
|
||
| When testing new features before rolling them out to users: | ||
|
|
||
| 1. **Create a feature branch** (recommended naming: `feature/description`) | ||
| ```bash | ||
| git checkout -b feature/my-feature | ||
| ``` | ||
|
|
||
| 2. **Make your changes locally** in the `src/` directory (edit the files on your machine) | ||
|
|
||
| 3. **Push to Apps Script and test** | ||
| ```bash | ||
| # Push changes to your Apps Script project | ||
| clasp push | ||
|
|
||
| # This updates your personal Apps Script deployment | ||
| # Now open a Google Sheet and test the add-on there | ||
| # The code runs in Google Apps Script, not on your local machine | ||
| ``` | ||
|
|
||
| 4. **Once verified, merge to main** | ||
| ```bash | ||
| git push origin feature/my-feature | ||
| # Create PR and merge to main | ||
| # GitHub Actions will automatically deploy to production | ||
| ``` | ||
|
|
||
| **Note:** The current workflow deploys directly to production on every push to `main`. Testing on feature branches with `clasp push` allows you to validate changes in a real Google Sheet before they go live to all users. | ||
|
|
Owner
Author
There was a problem hiding this comment.
This should be like, 5 lines max.
Also, does our current workflow push to production, or does it just push to testing? Because if testing actually requires UI input on the Apps Script side of things, then I assume our current clasp push isn't pushing changes to prod all at once.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the recommended workflow for testing new features before rolling them out to users. The strategy uses feature branches with local clasp push for validation before merging to main and auto-deploying to production.
Closes #7