shannon
Shannon is an AI pentester for web applications and APIs. It analyzes your source code, identifies attack vectors, and executes real exploits to prove vulnerabilities before they reach production.
- 52k
- TypeScript
- AGPL-3.0
- 7 h ago
various battle tested github workflows
Repo kanakkholwal/github-workflows, read from GitHub 1 min ago. kanakkholwal has not joined Take My Repo.
kanakkholwal/github-workflows is a public repo on GitHub by kanakkholwal. various battle tested github workflows. It declares no license on GitHub. Public does not mean open source: without a license, nobody is granted the right to reuse it. It has 0 stars and last changed on 2026-02-03. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-21.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
An open-source collection of reusable GitHub Actions workflow templates for deploying applications to various cloud platforms and services.
This repository provides production-ready GitHub Actions workflow templates that you can copy and customize for your projects. Whether you're deploying to Vercel, Google Cloud Platform, or other services, these templates offer battle-tested CI/CD patterns.
Available Templates:
express-to-vercel.yml)Deploy web applications to Vercel with automatic production and preview deployments. Works with any framework supported by Vercel (Next.js, Express, React, Vue, etc.).
Features:
Usage:
# Copy to .github/workflows/deploy-vercel.yml name: Deploy to Vercel on: push: branches: [main] pull_request: branches: [main] workflow_dispatch: # ... rest of the workflow
Required Secrets:
VERCEL_TOKEN - Your Vercel authentication tokenVERCEL_ORG_ID - Your Vercel organization IDVERCEL_PROJECT_ID_CE_SERVER - Your Vercel project IDProject Structure:
This template assumes your application is in apps/server directory. Customize the working-directory in the workflow to match your project structure.
Customization:
defaults: run: working-directory: your-app-directory # Change this to match your structure
express-to-gcp-with-docker.yml)Deploy containerized applications to Google Cloud Run using Docker images stored in Google Container Registry. Suitable for any application that can be containerized.
Features:
Usage:
# Copy to .github/workflows/deploy-gcp-docker.yml name: Deploy to GCP with Docker on: push: branches: [main, staging] workflow_dispatch: # ... rest of the workflow
Required Secrets:
CREDENTIALS_JSON - GCP service account credentials (JSON)GCP_PROJECT_ID - Your GCP project IDGCP_PROJECT_REGION - GCP region for deployment (e.g., us-central1)Project Structure:
This template assumes your application is in apps/server directory with a Dockerfile. Adjust paths in the workflow to match your structure.
Customization:
# Update the paths in the workflow paths: - 'your-app/**' # Trigger only on changes to your app directory # Update Docker build context docker build -f "your-app/Dockerfile" -t "${IMAGE_NAME}" "your-app"
express-to-gcp-with-source.yml)Deploy applications directly to Google Cloud Run from source code without building Docker images locally. Cloud Run will handle the containerization automatically.
Features:
Usage:
# Copy to .github/workflows/deploy-gcp-source.yml name: Deploy to GCP from Source on: workflow_dispatch: # ... rest of the workflow
Required Secrets:
CREDENTIALS_JSON - GCP service account credentials (JSON)GCP_PROJECT_REGION - GCP region for deploymentProject Structure:
This template assumes your application is in apps/server directory. Update the --source path in the workflow to match your application directory.
Customization:
# Update source path gcloud run deploy ${{ env.SERVICE_NAME_SERVER }} \ --source ./your-app-directory \ --region ${{ secrets.GCP_PROJECT_REGION }}
express-to-gcp-with-remote-container-registry.yml)Deploy to GCP Cloud Run using GitHub Container Registry (GHCR) as an intermediate registry, leveraging GCP's remote repository feature for seamless integration.
Features:
Usage:
# Copy to .github/workflows/deploy-gcp-ghcr.yml name: Deploy to GCP via GHCR on: push: branches: [main, staging] workflow_dispatch: # ... rest of the workflow
Required Secrets:
CREDENTIALS_JSON - GCP service account credentials (JSON)GCP_PROJECT_ID - Your GCP project IDGCP_PROJECT_NUMBER - Your GCP project numberGHCR_TOKEN - GitHub Personal Access Token with packages:write permissionRequired Variables:
GCP_REPO_REGION - GCP Artifact Registry region (e.g., us-central1)GCP_SERVING_REGION - GCP Cloud Run serving regionProject Structure:
This template assumes your application is in apps/server directory with a Dockerfile. Customize the context and file paths in the workflow.
Customization:
# Update Docker build context with: context: ./your-app-directory file: ./your-app-directory/Dockerfile
For Vercel Deployments:
For GCP Deployments:
Go to your repository โ Settings โ Secrets and variables โ Actions โ New repository secret
For Vercel:
VERCEL_TOKEN=<your-vercel-token>
VERCEL_ORG_ID=<your-org-id>
VERCEL_PROJECT_ID_CE_SERVER=<your-project-id>
For GCP:
CREDENTIALS_JSON=<service-account-json>
GCP_PROJECT_ID=<project-id>
GCP_PROJECT_REGION=<region>
GCP_PROJECT_NUMBER=<project-number> # For GHCR workflow
For GHCR:
GHCR_TOKEN=<github-personal-access-token>
Go to your repository โ Settings โ Secrets and variables โ Actions โ Variables
GCP_REPO_REGION=us-central1
GCP_SERVING_REGION=us-central1
# Create service account gcloud iam service-accounts create github-actions \ --display-name="GitHub Actions" # Grant necessary permissions gcloud projects add-iam-policy-binding PROJECT_ID \ --member="serviceAccount:github-actions@PROJECT_ID.iam.gserviceaccount.com" \ --role="roles/run.admin" gcloud projects add-iam-policy-binding PROJECT_ID \ --member="serviceAccount:github-actions@PROJECT_ID.iam.gserviceaccount.com" \ --role="roles/iam.serviceAccountUser" gcloud projects add-iam-policy-binding PROJECT_ID \ --member="serviceAccount:github-actions@PROJECT_ID.iam.gserviceaccount.com" \ --role="roles/storage.admin" # Create and download key gcloud iam service-accounts keys create key.json \ --iam-account=github-actions@PROJECT_ID.iam.gserviceaccount.com
github-workflows/
โโโ deployments/ # Workflow template files
โ โโโ express-to-vercel.yml
โ โโโ express-to-gcp-with-docker.yml
โ โโโ express-to-gcp-with-source.yml
โ โโโ express-to-gcp-with-remote-container-registry.yml
โโโ README.md # This file
deployments/ directory.github/workflows/ directory# 1. Navigate to your project cd your-project # 2. Create workflows directory if it doesn't exist mkdir -p .github/workflows # 3. Download or copy the workflow template curl -o .github/workflows/deploy-vercel.yml \ https://raw.githubusercontent.com/kanakkholwal/github-workflows/main/deployments/express-to-vercel.yml # 4. Customize the workflow file to match your project structure # Edit paths, working directories, and other configuration as needed # 5. Configure secrets in GitHub # Go to: Repository โ Settings โ Secrets and variables โ Actions # Add: VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID_CE_SERVER # 6. Commit and push git add .github/workflows/deploy-vercel.yml git commit -m "Add Vercel deployment workflow" git push
You can also use this repository as a template:
These templates are designed to be customized for your specific needs. Here are common customization patterns:
All templates assume an apps/server directory structure. Update paths to match your project:
# Change working directory defaults: run: working-directory: path/to/your/app # Update path filters on: push: paths: - 'your-app/**' # Update Docker context context: ./your-app-directory
Inject environment variables into your deployment:
- name: Deploy run: your-deploy-command env: DATABASE_URL: ${{ secrets.DATABASE_URL }} API_KEY: ${{ secrets.API_KEY }} NODE_ENV: production
Trigger deployments only when specific files or directories change:
on: push: branches: [main] paths: - 'src/**' - 'package.json' - 'Dockerfile'
Deploy to different environments based on branches:
- name: Set Environment run: | if [ "${{ github.ref }}" == "refs/heads/main" ]; then echo "ENV=production" >> $GITHUB_ENV elif [ "${{ github.ref }}" == "refs/heads/staging" ]; then echo "ENV=staging" >> $GITHUB_ENV fi - name: Deploy run: deploy-to-${{ env.ENV }}
We welcome contributions from the community! Help us expand this collection of workflow templates.
git checkout -b feature/add-aws-workflow)deployments/ directorygit push origin feature/add-aws-workflow)Use descriptive names that indicate the source type and destination:
[framework/app-type]-to-[platform]-[optional-method].ymlnextjs-to-vercel.yml, django-to-aws-ecs.yml, react-to-netlify.ymlThis project is open source and available under the MIT License.
Feel free to use these workflows in your personal or commercial projects. Attribution is appreciated but not required.
If you encounter problems with any workflow template:
This repository was created to provide developers with:
New to GitHub Actions? Check out these resources:
This is an active open-source project. We regularly:
Star this repository to stay updated with new workflows and improvements!
Made with โค๏ธ by the community, for the community
kanakkholwal/github-workflows is a public repo on GitHub by kanakkholwal. various battle tested github workflows.
It declares no license on GitHub. Public does not mean open source: without a license, nobody is granted the right to reuse it.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-02-03. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.

Shannon is an AI pentester for web applications and APIs. It analyzes your source code, identifies attack vectors, and executes real exploits to prove vulnerabilities before they reach production.
Harness Open Source is an end-to-end developer platform with Source Control Management, CI/CD Pipelines, Hosted Developer Environments, and Artifact Registries.
High-performance PDF toolkit that runs entirely in your browser
Animated, accessible, and customizable components for React and Svelte.


Markdown Editor with React + TS + shadcn UI / Tailwind css
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/kanakkholwal/github-workflowsTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.