Replace Hardcoded Contract ID and Deployer Identity With Configurable Values
Description
rontend.yml has hardcoded VITE_CONTRACT_ID and VITE_RPC_URL env vars. Makefile has hardcoded rellis-deployer identity name. These must be updated manually after each redeployment, creating maintenance burden.
Requirements & Context
Move to GitHub Actions secrets or environment variables. Use repo-level variables for contract ID. Add Makefile variable for deployer identity.
Suggested Execution
Branch: ix/ci-remove-hardcoded-values
Implement Changes
(1) Replace hardcoded vars in frontend.yml with secrets (2) Make deployer identity a Makefile variable (3) Document required secrets in setup guide (4) Add validation step
Test & Commit
Trigger workflow, verify it uses secrets/variables instead of hardcoded values.
Example Commit Message
ix(ci): replace hardcoded contract ID and deployer identity with configurable variables and secrets
Guidelines
- Use GitHub Secrets for sensitive values
- Use GitHub Variables for non-sensitive configuration
Replace Hardcoded Contract ID and Deployer Identity With Configurable Values
Description
rontend.yml has hardcoded VITE_CONTRACT_ID and VITE_RPC_URL env vars. Makefile has hardcoded rellis-deployer identity name. These must be updated manually after each redeployment, creating maintenance burden.
Requirements & Context
Move to GitHub Actions secrets or environment variables. Use repo-level variables for contract ID. Add Makefile variable for deployer identity.
Suggested Execution
Branch: ix/ci-remove-hardcoded-values
Implement Changes
(1) Replace hardcoded vars in frontend.yml with secrets (2) Make deployer identity a Makefile variable (3) Document required secrets in setup guide (4) Add validation step
Test & Commit
Trigger workflow, verify it uses secrets/variables instead of hardcoded values.
Example Commit Message
ix(ci): replace hardcoded contract ID and deployer identity with configurable variables and secrets
Guidelines