chore: exclude .vscode from WordPress SVN releases#6
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Add .vscode/ to .gitattributes export-ignore - Add --exclude='.vscode' to deploy.yml rsync as safety net Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Update all existing class filenames to match the actual codebase naming convention (e.g. class-chip-givewp-api.php, not class-api.php). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
What does this change?
This PR focuses on repository hygiene and long-term architectural planning for the CHIP for GiveWP plugin.
Key changes include:
.vscode/to.gitattributeswith theexport-ignoreattribute and updated the GitHub Actions deployment workflow (deploy.yml) to include--exclude='.vscode'in thersynccommand. This prevents local workspace settings from being included ingit archiveoutputs or shipped to the WordPress.org SVN trunk.docs/recurring-feasibility.md, a comprehensive technical roadmap. This document analyzes the CHIP "Charge Token API," outlines necessary GiveWP hooks for both legacy and v3 visual forms, and provides a risk assessment for implementing subscription logic (scheduler, dunning, and token management).How to test
git archive -o latest.zip HEADand inspect the resulting ZIP file to confirm the.vscodefolder is excluded..github/workflows/deploy.ymlto ensure the--exclude='.vscode'flag is correctly positioned within thersyncoptions.docs/recurring-feasibility.mdto verify that the technical assumptions regarding GiveWP’s Recurring Donations add-on and CHIP’s tokenization flow are accurate.Potential Risks & Review Items
rsyncexclude syntax indeploy.ymldoesn't interfere with existing exclusions.Is this PR safe for automatic approval?
Yes. The changes are limited to repository configuration (ignoring IDE files) and adding a documentation-only markdown file.
Images
Related Tasks / PRs
Checklist