Git Notes
HubBenefits of Git and GitHub - Why They MatterGit vs GitHubVersion Control SystemWhat Is GitWhat Is GitHubConfigure Git - User Identity and SettingsCreate GitHub Account - Sign Up GuideFirst Git Repository - Getting StartedInstall Git on Linux - Complete Setup GuideInstall Git on macOS - Installation GuideInstall Git on Windows - Step-by-Step GuideGit Add - Stage ChangesGit Clone - Copy Remote Repositories LocallyGit Commit - Save ChangesGit Diff - Compare Changes in Your RepositoryGit Ignore - Exclude Files from Version ControlGit Init - Initialize RepositoryGit Log - View Commit HistoryGit Status - Check Repository StateGit Fetch - Download Remote Changes Without MergingGit Pull - Fetch and Merge Remote ChangesGit Push - Upload Local Commits to Remote RepositoryGit Remote - Manage Remote Repository ConnectionsLocal Repository - Understanding Your Git Working EnvironmentRemote Repository - Collaborate Through Shared RepositoriesSync Local and Remote - Keep Repositories in HarmonyAmend Commit - Fix Last CommitDelete Branch - Clean Up BranchesGit Reset - Move HEAD and Undo CommitsGit Restore - Discard ChangesGit Revert - Safely Undo ChangesRecover Lost Commits - Reflog GuideFork RepositoryGitHub PagesGitHub Profile SetupGitHub RepositoriesGitHub Stars and WatchersRepository SettingsCode ReviewsGit CloneGit FetchGit PullGit PushGitHub IssuesLabels and MilestonesOpen Source ContributionsGitHub Project BoardsPull Requests - Propose and Review Code ChangesTeam Collaboration with Git and GitHubAutomated Testing with GitHub ActionsCI/CD with GitHub ActionsDeployment Automation with GitHub ActionsIntroduction to GitHub ActionsGitHub Actions RunnersGitHub Actions WorkflowsEnterprise Git Workflows - Scale Git for Large OrganizationsFeature Branch Workflow - Isolate Development WorkGitFlow Workflow - Structured Release ManagementMonorepo Workflow - Manage Multiple Projects in One RepositoryTrunk-Based Development - Ship Code Fast and SafelyDeployment WorkflowsGitHub Pages DeploymentNetlify Deployment from GitHubRender Deployment from GitHubVercel Deployment from GitHubBranch Protection Rules - Secure Your Git BranchesPersonal Access Tokens - Authenticate with GitHubRepository Security Best PracticesSecret Scanning - Detect Leaked Credentials in CodeSigned Commits - Verify Commit Authenticity with GPGSSH Keys - Secure Git Authentication Without PasswordsGit Bisect - Find Bugs with Binary SearchGit Cherry-Pick - Apply Specific Commits to Any BranchGit Hooks - Automate Workflows with Git EventsGit Internals - Understanding How Git Works Under the HoodGit Stash - Temporarily Save Uncommitted ChangesGit Submodules - Manage External Dependencies as Git ReposGit Tag - Mark Important Points in HistoryGit Worktrees - Work on Multiple Branches SimultaneouslyCollaborative Web App ProjectComplete Team Workflow ProjectGitHub Actions Project - Build a CI/CD PipelineOpen Source Project Contribution - Guided ExercisePortfolio Project with Git - Showcase Your SkillsGit Command CheatsheetGit Interview Questions - Comprehensive Preparation GuideGitHub Interview QuestionsScenario-Based Git Interview QuestionsGit Troubleshooting GuideGit Best Practices - Professional Development HabitsCommon Git Errors and Fixes - Quick SolutionsGit Command Reference - Complete Command GuideLearning Resources - Continue Your Git & GitHub EducationBranch Strategies - Choosing the Right Git Branching ModelCreate Branch in Git - Start New Development LinesFast-Forward Merge in Git - Clean Linear HistoryGit BranchGit CheckoutGit MergeGit RebaseMerge Branches in Git - Combine Development WorkMerge Conflicts - Resolve Git Conflicts Like a ProSwitch Branch in Git - Navigate Between Branches
Deployment automation removes the human from the deployment process, replacing manual steps with reliable, repeatable workflows. With GitHub Actions, you...
Deployment automation removes the human from the deployment process, replacing manual steps with reliable, repeatable workflows. With GitHub Actions, you can automatically deploy your application whenever code is merged, a release is published, or a tag is created. This eliminates deployment anxiety — the process is the same every time, reducing errors and freeing developers to focus on building features rather than managing releases.
Why Automate Deployments
Manual deployments are error-prone. They require someone to remember the correct sequence of commands, the right server credentials, and the proper configuration for each environment. Automated deployments provide:
- Consistency — The same steps execute identically every time
- Speed — Deploy in minutes instead of hours
- Auditability — Every deployment is logged with who triggered it and what was deployed
- Confidence — If it worked last time, it works this time
- Frequency — Deploy daily or hourly instead of monthly
Deploying to Cloud Platforms
AWS S3 and CloudFront (Static Sites)
Example
name: Deploy to AWS
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci && npm run build
- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@v4
with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws-region: us-east-1
- name: Sync to S3
run: aws s3 sync dist/ s3://my-bucket --delete
- name: Invalidate CloudFront cache
run: |
aws cloudfront create-invalidation \
--distribution-id ${{ secrets.CLOUDFRONT_ID }} \
--paths "/*"
Docker Container to AWS ECS
Example
name: Deploy Container
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Login to Amazon ECR
uses: aws-actions/amazon-ecr-login@v2
- name: Build and push Docker image
run: |
docker build -t my-app:${{ github.sha }} .
docker tag my-app:${{ github.sha }} $ECR_REGISTRY/my-app:latest
docker push $ECR_REGISTRY/my-app:latest
- name: Update ECS service
run: |
aws ecs update-service \
--cluster production \
--service my-app \
--force-new-deployment
Deploy to a VPS via SSH
Example
name: Deploy to Server
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- name: Deploy via SSH
uses: appleboy/ssh-action@v1
with:
host: ${{ secrets.SERVER_HOST }}
username: ${{ secrets.SERVER_USER }}
key: ${{ secrets.SSH_PRIVATE_KEY }}
script: |
cd /var/www/my-app
git pull origin main
npm ci --production
npm run build
pm2 restart my-app
Release-Based Deployments
Trigger deployments when you publish a GitHub release:
Example
on:
release:
types: [published]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- name: Deploy version ${{ github.event.release.tag_name }}
run: |
echo "Deploying ${{ github.event.release.tag_name }}"
npm run deploy -- --version=${{ github.event.release.tag_name }}
Multi-Environment Deployments
Deploy to staging first, then production after approval:
yaml example
jobs:
deploy-staging:
runs-on: ubuntu-latest
environment: staging
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- run: deploy-to-staging.sh
deploy-production:
needs: deploy-staging
runs-on: ubuntu-latest
environment:
name: production
url: https://myapp.com
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- run: deploy-to-production.shThe production environment can require manual approval — someone must click "Approve" in GitHub before the production deployment runs.
Database Migrations
Include database migrations as part of deployment:
yaml example
- name: Run database migrations
run: npx prisma migrate deploy
env:
DATABASE_URL: ${{ secrets.DATABASE_URL }}
- name: Verify migration success
run: npx prisma db seed --checkAlways run migrations before deploying the new application code to ensure the database schema matches what the new code expects.
Health Checks After Deployment
Verify the deployment succeeded:
Example
- name: Health check
run: |
for i in {1..10}; do
STATUS=$(curl -s -o /dev/null -w "%{http_code}" https://myapp.com/health)
if [ "$STATUS" = "200" ]; then
echo "Health check passed!"
exit 0
fi
echo "Waiting for service to be healthy... (attempt $i)"
sleep 10
done
echo "Health check failed after 10 attempts"
exit 1
- name: Rollback on failure
if: failure()
run: |
echo "Deployment failed, rolling back..."
# Rollback commands here
Deployment Notifications
Keep the team informed:
yaml example
- name: Notify successful deployment
if: success()
run: |
curl -X POST ${{ secrets.SLACK_WEBHOOK }} \
-H "Content-Type: application/json" \
-d '{"text": "✅ Deployed ${{ github.sha }} to production by ${{ github.actor }}"}'
- name: Notify failed deployment
if: failure()
run: |
curl -X POST ${{ secrets.SLACK_WEBHOOK }} \
-H "Content-Type: application/json" \
-d '{"text": "❌ Deployment failed! Check: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"}'Key Takeaways
Deployment automation with GitHub Actions transforms deployment from a risky, manual event into a routine, reliable process. Start with simple push-to-deploy workflows and progressively add sophistication — multi-environment stages, approval gates, health checks, and automatic rollbacks. The goal is to make deployment boring — something that happens multiple times daily without anyone worrying about it, because the automation handles all the complexity.
Exam Focus
Revise definitions, diagrams, examples, and short-answer points for Deployment Automation with GitHub Actions.
Interview Use
Prepare one clear explanation, one practical example, and one common mistake for this Git & GitHub topic.
Search Terms
git-github, git & github, git, github, actions, deployment, automation, deployment automation with github actions
Related Git & GitHub Topics
Continue learning this concept
Github ActionsAutomated Testing with GitHub ActionsAutomated testing is the practice of running your test suite automatically every time code changes, without any human intervention. GitHub Actions makes...Github ActionsCI/CD with GitHub ActionsContinuous Integration and Continuous Deployment (CI/CD) is the backbone of modern software delivery. CI ensures that every code change is automatically...Github ActionsIntroduction to GitHub ActionsGitHub Actions is a powerful automation platform built directly into GitHub that lets you create custom workflows triggered by events in your repository....Github ActionsGitHub Actions RunnersRunners are the machines that execute your GitHub Actions workflows. When a workflow is triggered, GitHub assigns it to a runner that has the appropriate...Github ActionsGitHub Actions WorkflowsWorkflows are the heart of GitHub Actions — they define what happens, when it happens, and how it happens. A workflow is an automated process described in a...DeploymentDeployment WorkflowsDeployment workflows define how your code travels from a developer\