-
Notifications
You must be signed in to change notification settings - Fork 1
85 lines (72 loc) · 2.46 KB
/
CI.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
# This is a basic workflow to help you get started with Actions
name: CI
# Controls when the workflow will run
on:
# Triggers the workflow on push or pull request events but only for the "main" branch
push:
branches: [ "*" ]
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# Build job
build:
# The type of runner that the job will run on
runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- name: Checkout code
uses: actions/checkout@v3
with:
node-version: 18
# Install dependencies
- name: Install dependencies
run: npm install
# Run tests
- name: Run tests
run: npm test
# Print a message
- name: Print a message
run: echo Hello, world!
# Print multi-line message
- name: Print multi-line message
run: |
echo Add other actions to build,
echo test, and deploy your project.
# Merge branches job
merge-branches:
runs-on: ubuntu-latest
steps:
# Checkout code
- name: Checkout code
uses: actions/checkout@v2
# Merge branches
- name: Merge branches
run: |
# Assuming the current branch is main
git config --global user.email "[email protected]"
git config --global user.name "Jalish Chauhan"
git fetch origin
git checkout main
git merge --no-ff --allow-unrelated-histories ${{ github.ref }}
if ! git merge --no-ff ${{ github.ref }}; then
echo "Error: Merge conflict occurred. Please resolve the conflicts and try again."
exit 1
fi
git push origin main
# Deployment job
deploy:
runs-on: ubuntu-latest
needs: [build] # Waits for the 'build' job to complete before starting this job
steps:
# Deploy to production
- name: Deploy to production
uses: actions/checkout@v2
# Use render-deploy-action for deployment
- name: Render Deploy Action
uses: johnbeynon/[email protected]
with:
service-id: srv-co8egfv109ks73ed9fv0?key=zOkL3z42FtA
api-key: rnd_ztF9piodvNQ3byZ1AZiy9KUJFu9l
wait-for-success: true