feat: add continuous deployment workflow for xdai.io (#203)#294
Open
15414tdh wants to merge 1 commit into
Open
feat: add continuous deployment workflow for xdai.io (#203)#29415414tdh wants to merge 1 commit into
15414tdh wants to merge 1 commit into
Conversation
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.
Summary
Added a GitHub Actions continuous deployment workflow that automatically deploys the burner-wallet to xdai.io on push to master, as requested in issue #203.
Changes
.github/workflows/deploy.ymlwith:workflow_dispatchfor testingnpm cixdai.iodomainDeployment Flow
Required Secrets
The maintainer must configure these repository secrets:
PINATA_API_KEY/PINATA_SECRET_KEY– for IPFS pinningCLOUDFLARE_ZONE/CLOUDFLARE_API_TOKEN– for DNSLink updatesNote
Based on the LeapDAO approach (leapdao#144) — they successfully use IPFS + DNSLink for burner-wallet deployment. This keeps production risk low since only merged master changes are deployed, and manual trigger allows testing before merge.
Closes #203
/claim