Skip to content

ci(ci-cd): planning for teh implemntation of ci-cd#1

Open
Viscous106 wants to merge 2 commits into
mainfrom
ci-cd
Open

ci(ci-cd): planning for teh implemntation of ci-cd#1
Viscous106 wants to merge 2 commits into
mainfrom
ci-cd

Conversation

@Viscous106

Copy link
Copy Markdown
Contributor

planning:

  • first we will review the planning
  • then we are going to implemet it and at the end close the pr

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation to guide AI-assisted contributions and to lay out a proposed CI/CD approach for the broader Mergit project (workflows, environments, deployment strategy).

Changes:

  • Introduces CLAUDE.md with repository purpose, architecture summary (from PRD), and contribution conventions.
  • Adds a detailed ci-cd.md CI/CD implementation plan including suggested GitHub Actions workflows, secret/env setup, and deployment steps.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 10 comments.

File Description
CLAUDE.md Adds Claude Code guidance + summarized architecture/conventions for the project.
ci-cd.md Adds an end-to-end CI/CD planning document with workflow examples, secret management, and deploy steps.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread CLAUDE.md Outdated

## Repository Purpose

This is the documentation repository for **Mergit** — an AI agent economy platform built for a Monad blockchain hackathon. It currently contains only the Product Requirements Document (`PRD.md`). All implementation lives (or will live) in separate repositories under the `mergit-io` GitHub organization.
Comment thread ci-cd.md
- **2 AMD x86 VMs:** 1 OCPU + 1 GB RAM each (too small for most Mergit services — use ARM)
- **200 GB block storage total**
- **10 TB outbound bandwidth/month**
- No credit card required to continue after trial ends
Comment thread ci-cd.md
Comment on lines +105 to +108
# Port 22 (SSH) — source 0.0.0.0/0
# Port 80 (HTTP) — source 0.0.0.0/0
# Port 443 (HTTPS) — source 0.0.0.0/0
# Port 8000 (api-gateway, if no reverse proxy yet) — source 0.0.0.0/0
Comment thread ci-cd.md
uses: actions/cache@v4
with:
path: ~/.cache/uv
key: ${{ runner.os }}-uv-${{ hashFiles('services/orchestration/pyproject.toml') }}
Comment thread ci-cd.md
Comment on lines +734 to +738
deploy:
name: Deploy to Staging
needs: [build-rust, build-python, build-frontend]
runs-on: ubuntu-latest
environment: staging # uses STAGING_* secrets
Comment thread ci-cd.md
Comment on lines +919 to +923
deploy:
name: Deploy to Production
needs: [build-rust, build-python, build-frontend]
runs-on: ubuntu-latest
environment: production # ← PAUSES HERE until you approve in GitHub UI
Comment thread ci-cd.md
Comment on lines +1046 to +1050
MONAD_RPC_HTTP: ${{ secrets.PROD_MONAD_RPC_HTTP }}
DEPLOYER_PRIVATE_KEY: ${{ secrets.PROD_DEPLOYER_PRIVATE_KEY }}
IDENTITY_SERVICE_ADDRESS: ${{ secrets.IDENTITY_SERVICE_ADDRESS }}
INDEXER_ORACLE_ADDRESS: ${{ secrets.INDEXER_ORACLE_ADDRESS }}
MONAD_EXPLORER_API_KEY: ${{ secrets.MONAD_EXPLORER_API_KEY }}
Comment thread ci-cd.md
Comment on lines +252 to +255
| `PROD_MONAD_RPC_HTTP` | Monad RPC URL |
| `PROD_MONAD_RPC_WSS` | Monad WSS URL |
| `PROD_DEPLOYER_PRIVATE_KEY` | Deployer wallet private key (for contract deployments — handle with extreme care) |
| `PROD_ORACLE_KEYSTORE_PASSWORD` | Password for the encrypted oracle keystore file |
Comment thread ci-cd.md
--rpc-url $MONAD_RPC_HTTP \
--private-key $DEPLOYER_PRIVATE_KEY \
--broadcast --verify \
--verifier-url https://testnet.monadexplorer.com/api
Comment thread ci-cd.md

### 10.1 cd-staging.yml

Triggers on every push to `develop`. Builds all Docker images, pushes them to ghcr.io tagged `:staging`, then SSH's into the staging VM and rolls the stack.
@shri771

shri771 commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

@Viscous106, Why do we need ci/cd at this stage of project?

@Viscous106

Copy link
Copy Markdown
Contributor Author

@Viscous106, Why do we need ci/cd at this stage of project?

What kind of question is that ?? @shri771

@Viscous106

Copy link
Copy Markdown
Contributor Author

@Viscous106, Why do we need ci/cd at this stage of project?

Becows Having cicd makes maintainer's work easy. And i want it from the very start to improvise it on the way i use it @shri771

@Viscous106 Viscous106 added the enhancement New feature or request label Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants