@toptal/davinci-workflow 1.9.0 → 1.9.1-alpha-chore-implement-documentation-buid.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -18,38 +18,1642 @@ or
18
18
 
19
19
  Arguments:
20
20
 
21
- - `workflow-name` - the name of the GH workflow to create
21
+ * `workflow-name` - the name of the GH workflow to create
22
22
 
23
23
  ## GH Workflows
24
24
 
25
- - `typecheck` — Check an App on Typescript issues. Example: `davinci new-workflow typecheck`
26
- - `lint` Check app for Lint issues. Example: `davinci new-workflow lint`
27
- - `unit-tests` — Conduct Unit tests. Example: `davinci new-workflow unit-tests`
28
- - `danger` - Run check on PR title and commit messages for compliance. Example `davinci new-workflow danger`
29
- - `alpha-package` - Execute script to publish alpha version of package to NPM. Example `davinci new-workflow alpha-package`
30
- Example of usage in PR: write a new comment in PR
31
- `@toptal-bot run package:alpha-release` — it runs [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
32
- - `deploy-temploy` - Builds & Deploys application to Temploy. It creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
33
- Example of usage in PR: write a new comment in PR: `@toptal-bot run temploy`
34
- - `deploy` — Performs docker image build and deployment to staging/production environment. Consists of three Workflows:
35
- - `Deploy` (davinci-deploy.yml)
36
- - it's triggered when PR is merged to `master` or `main` branch
37
- - It builds and pushes a new instance of Docker image to google cloud
38
- - if `davinci.yml` is present in the root folder:
39
- - and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
40
- - and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
41
- - `Deploy to staging` (davinci-deploy-staging.yml)
42
- - Triggers Jenkins job for deployment to staging environment
43
- - how to trigger the Workflow manually:
44
- - add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
45
- - In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
46
- - `Deploy to production` (davinci-deploy-production.yml)
47
- - Triggers Jenkins job for deployment to production environment
48
- - how to trigger the Workflow manually:
49
- - In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
50
- - Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
51
-
25
+ ## alpha-package
26
+ Executes script to publish alpha version of package to NPM
27
+
28
+ **Example:**
29
+ ```bash
30
+ $ davinci new-workflow alpha-package
31
+ ```
32
+ **Description:**
33
+
34
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
35
+
36
+ **Example of usage:**
37
+
38
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
39
+
40
+ ## typecheck
41
+ Checks an App on Typescript issues
42
+
43
+ **Example:**
44
+ ```bash
45
+ $ davinci new-workflow typecheck
46
+ ```
47
+ **Description:**
48
+
49
+ it triggers `typecheck` GH Action
50
+
51
+
52
+
53
+ ## lint
54
+ Checks an App for lint issues
55
+
56
+ **Example:**
57
+ ```bash
58
+ $ davinci new-workflow lint
59
+ ```
60
+ **Description:**
61
+
62
+ it triggers `lint` GH Action
63
+
64
+
65
+
66
+ ## unit-tests
67
+ Conducts unit tests
68
+
69
+ **Example:**
70
+ ```bash
71
+ $ davinci new-workflow unit-tests
72
+ ```
73
+ **Description:**
74
+
75
+ it triggers `unit-tests` GH Action
76
+
77
+
78
+
79
+ ## integration-tests
80
+ Conducts integration tests in a project using Cypress.
81
+
82
+ **Example:**
83
+ ```bash
84
+ $ davinci new-workflow integration-tests
85
+ ```
86
+ **Description:**
87
+
88
+ it triggers `integration-tests` GH Action
89
+
90
+
91
+
92
+ ## danger
93
+ Checks if the PR title and commit messages comply with Toptal's standards
94
+
95
+ **Example:**
96
+ ```bash
97
+ $ davinci new-workflow danger
98
+ ```
99
+ **Description:**
100
+
101
+ it triggers `danger` GH Action
102
+
103
+
104
+
105
+ ## deploy-temploy
106
+ Builds & Deploys application to Temploy
107
+
108
+ **Example:**
109
+ ```bash
110
+ $ davinci new-workflow deploy-temploy
111
+ ```
112
+ **Description:**
113
+
114
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
115
+
116
+ **Example of usage:**
117
+
118
+ Write a new comment in PR `@toptal-bot run temploy`
119
+
120
+ ## deploy
121
+ Performs docker image build and deployment to staging/production environment
122
+
123
+ **Example:**
124
+ ```bash
125
+ $ davinci new-workflow deploy
126
+ ```
127
+ **Description:**
128
+
129
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
130
+
131
+ * `Deploy` (davinci-deploy.yml)
132
+ * it's triggered when PR is merged to `master` or `main` branch
133
+ * It builds and pushes a new instance of Docker image to google cloud
134
+ * if `davinci.yml` is present in the root folder:
135
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
136
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
137
+ * `Deploy to staging` (davinci-deploy-staging.yml)
138
+ * Triggers Jenkins job for deployment to staging environment
139
+ * how to trigger the Workflow manually:
140
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
141
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
142
+ * `Deploy to production` (davinci-deploy-production.yml)
143
+ * Triggers Jenkins job for deployment to production environment
144
+ * how to trigger the Workflow manually:
145
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
146
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
147
+
148
+
149
+
150
+ ## alpha-package
151
+
152
+ Executes script to publish alpha version of package to NPM
153
+
154
+ **Example:**
155
+
156
+ ```bash
157
+ $ davinci new-workflow alpha-package
158
+ ```
159
+
160
+ **Description:**
161
+
162
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
163
+
164
+ **Example of usage:**
165
+
166
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
167
+
168
+ ## typecheck
169
+
170
+ Checks an App on Typescript issues
171
+
172
+ **Example:**
173
+
174
+ ```bash
175
+ $ davinci new-workflow typecheck
176
+ ```
177
+
178
+ **Description:**
179
+
180
+ it triggers `typecheck` GH Action
181
+
182
+ ## lint
183
+
184
+ Checks an App for lint issues
185
+
186
+ **Example:**
187
+
188
+ ```bash
189
+ $ davinci new-workflow lint
190
+ ```
191
+
192
+ **Description:**
193
+
194
+ it triggers `lint` GH Action
195
+
196
+ ## unit-tests
197
+
198
+ Conducts unit tests
199
+
200
+ **Example:**
201
+
202
+ ```bash
203
+ $ davinci new-workflow unit-tests
204
+ ```
205
+
206
+ **Description:**
207
+
208
+ it triggers `unit-tests` GH Action
209
+
210
+ ## integration-tests
211
+
212
+ Conducts integration tests in a project using Cypress.
213
+
214
+ **Example:**
215
+
216
+ ```bash
217
+ $ davinci new-workflow integration-tests
218
+ ```
219
+
220
+ **Description:**
221
+
222
+ it triggers `integration-tests` GH Action
223
+
224
+ ## danger
225
+
226
+ Checks if the PR title and commit messages comply with Toptal's standards
227
+
228
+ **Example:**
229
+
230
+ ```bash
231
+ $ davinci new-workflow danger
232
+ ```
233
+
234
+ **Description:**
235
+
236
+ it triggers `danger` GH Action
237
+
238
+ ## deploy-temploy
239
+
240
+ Builds & Deploys application to Temploy
241
+
242
+ **Example:**
243
+
244
+ ```bash
245
+ $ davinci new-workflow deploy-temploy
246
+ ```
247
+
248
+ **Description:**
249
+
250
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
251
+
252
+ **Example of usage:**
253
+
254
+ Write a new comment in PR `@toptal-bot run temploy`
255
+
256
+ ## deploy
257
+
258
+ Performs docker image build and deployment to staging/production environment
259
+
260
+ **Example:**
261
+
262
+ ```bash
263
+ $ davinci new-workflow deploy
264
+ ```
265
+
266
+ **Description:**
267
+
268
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
269
+
270
+ * `Deploy` (davinci-deploy.yml)
271
+ * it's triggered when PR is merged to `master` or `main` branch
272
+ * It builds and pushes a new instance of Docker image to google cloud
273
+ * if `davinci.yml` is present in the root folder:
274
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
275
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
276
+ * `Deploy to staging` (davinci-deploy-staging.yml)
277
+ * Triggers Jenkins job for deployment to staging environment
278
+ * how to trigger the Workflow manually:
279
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
280
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
281
+ * `Deploy to production` (davinci-deploy-production.yml)
282
+ * Triggers Jenkins job for deployment to production environment
283
+ * how to trigger the Workflow manually:
284
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
285
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
286
+
287
+ ## alpha-package
288
+
289
+ Executes script to publish alpha version of package to NPM!
290
+
291
+ **Example:**
292
+
293
+ ```bash
294
+ $ davinci new-workflow alpha-package
295
+ ```
296
+
297
+ **Description:**
298
+
299
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
300
+
301
+ **Example of usage:**
302
+
303
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
304
+
305
+ ## typecheck
306
+
307
+ Checks an App on Typescript issues
308
+
309
+ **Example:**
310
+
311
+ ```bash
312
+ $ davinci new-workflow typecheck
313
+ ```
314
+
315
+ **Description:**
316
+
317
+ it triggers `typecheck` GH Action
318
+
319
+ ## lint
320
+
321
+ Checks an App for lint issues
322
+
323
+ **Example:**
324
+
325
+ ```bash
326
+ $ davinci new-workflow lint
327
+ ```
328
+
329
+ **Description:**
330
+
331
+ it triggers `lint` GH Action
332
+
333
+ ## unit-tests
334
+
335
+ Conducts unit tests
336
+
337
+ **Example:**
338
+
339
+ ```bash
340
+ $ davinci new-workflow unit-tests
341
+ ```
342
+
343
+ **Description:**
344
+
345
+ it triggers `unit-tests` GH Action
346
+
347
+ ## integration-tests
348
+
349
+ Conducts integration tests in a project using Cypress.
350
+
351
+ **Example:**
352
+
353
+ ```bash
354
+ $ davinci new-workflow integration-tests
355
+ ```
356
+
357
+ **Description:**
358
+
359
+ it triggers `integration-tests` GH Action
360
+
361
+ ## danger
362
+
363
+ Checks if the PR title and commit messages comply with Toptal's standards
364
+
365
+ **Example:**
366
+
367
+ ```bash
368
+ $ davinci new-workflow danger
369
+ ```
370
+
371
+ **Description:**
372
+
373
+ it triggers `danger` GH Action
374
+
375
+ ## deploy-temploy
376
+
377
+ Builds & Deploys application to Temploy
378
+
379
+ **Example:**
380
+
381
+ ```bash
382
+ $ davinci new-workflow deploy-temploy
383
+ ```
384
+
385
+ **Description:**
386
+
387
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
388
+
389
+ **Example of usage:**
390
+
391
+ Write a new comment in PR `@toptal-bot run temploy`
392
+
393
+ ## deploy
394
+
395
+ Performs docker image build and deployment to staging/production environment
396
+
397
+ **Example:**
398
+
399
+ ```bash
400
+ $ davinci new-workflow deploy
401
+ ```
402
+
403
+ **Description:**
404
+
405
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
406
+
407
+ * `Deploy` (davinci-deploy.yml)
408
+ * it's triggered when PR is merged to `master` or `main` branch
409
+ * It builds and pushes a new instance of Docker image to google cloud
410
+ * if `davinci.yml` is present in the root folder:
411
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
412
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
413
+ * `Deploy to staging` (davinci-deploy-staging.yml)
414
+ * Triggers Jenkins job for deployment to staging environment
415
+ * how to trigger the Workflow manually:
416
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
417
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
418
+ * `Deploy to production` (davinci-deploy-production.yml)
419
+ * Triggers Jenkins job for deployment to production environment
420
+ * how to trigger the Workflow manually:
421
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
422
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
423
+
424
+ ## alpha-package
425
+
426
+ Executes script to publish alpha version of package to NPM
427
+
428
+ **Example:**
429
+
430
+ ```bash
431
+ $ davinci new-workflow alpha-package
432
+ ```
433
+
434
+ **Description:**
435
+
436
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
437
+
438
+ **Example of usage:**
439
+
440
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
441
+
442
+ ## typecheck
443
+
444
+ Checks an App on Typescript issues
445
+
446
+ **Example:**
447
+
448
+ ```bash
449
+ $ davinci new-workflow typecheck
450
+ ```
451
+
452
+ **Description:**
453
+
454
+ it triggers `typecheck` GH Action
455
+
456
+ ## lint
457
+
458
+ Checks an App for lint issues
459
+
460
+ **Example:**
461
+
462
+ ```bash
463
+ $ davinci new-workflow lint
464
+ ```
465
+
466
+ **Description:**
467
+
468
+ it triggers `lint` GH Action
469
+
470
+ ## unit-tests
471
+
472
+ Conducts unit tests
473
+
474
+ **Example:**
475
+
476
+ ```bash
477
+ $ davinci new-workflow unit-tests
478
+ ```
479
+
480
+ **Description:**
481
+
482
+ it triggers `unit-tests` GH Action
483
+
484
+ ## integration-tests
485
+
486
+ Conducts integration tests in a project using Cypress.
487
+
488
+ **Example:**
489
+
490
+ ```bash
491
+ $ davinci new-workflow integration-tests
492
+ ```
493
+
494
+ **Description:**
495
+
496
+ it triggers `integration-tests` GH Action
497
+
498
+ ## danger
499
+
500
+ Checks if the PR title and commit messages comply with Toptal's standards
501
+
502
+ **Example:**
503
+
504
+ ```bash
505
+ $ davinci new-workflow danger
506
+ ```
507
+
508
+ **Description:**
509
+
510
+ it triggers `danger` GH Action
511
+
512
+ ## deploy-temploy
513
+
514
+ Builds & Deploys application to Temploy
515
+
516
+ **Example:**
517
+
518
+ ```bash
519
+ $ davinci new-workflow deploy-temploy
520
+ ```
521
+
522
+ **Description:**
523
+
524
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
525
+
526
+ **Example of usage:**
527
+
528
+ Write a new comment in PR `@toptal-bot run temploy`
529
+
530
+ ## deploy
531
+
532
+ Performs docker image build and deployment to staging/production environment
533
+
534
+ **Example:**
535
+
536
+ ```bash
537
+ $ davinci new-workflow deploy
538
+ ```
539
+
540
+ **Description:**
541
+
542
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
543
+
544
+ * `Deploy` (davinci-deploy.yml)
545
+ * it's triggered when PR is merged to `master` or `main` branch
546
+ * It builds and pushes a new instance of Docker image to google cloud
547
+ * if `davinci.yml` is present in the root folder:
548
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
549
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
550
+ * `Deploy to staging` (davinci-deploy-staging.yml)
551
+ * Triggers Jenkins job for deployment to staging environment
552
+ * how to trigger the Workflow manually:
553
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
554
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
555
+ * `Deploy to production` (davinci-deploy-production.yml)
556
+ * Triggers Jenkins job for deployment to production environment
557
+ * how to trigger the Workflow manually:
558
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
559
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
560
+
561
+ ## alpha-package
562
+
563
+ Executes script to publish alpha version of package to NPM--
564
+
565
+ **Example:**
566
+
567
+ ```bash
568
+ $ davinci new-workflow alpha-package
569
+ ```
570
+
571
+ **Description:**
572
+
573
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
574
+
575
+ **Example of usage:**
576
+
577
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
578
+
579
+ ## typecheck
580
+
581
+ Checks an App on Typescript issues
582
+
583
+ **Example:**
584
+
585
+ ```bash
586
+ $ davinci new-workflow typecheck
587
+ ```
588
+
589
+ **Description:**
590
+
591
+ it triggers `typecheck` GH Action
592
+
593
+ ## lint
594
+
595
+ Checks an App for lint issues
596
+
597
+ **Example:**
598
+
599
+ ```bash
600
+ $ davinci new-workflow lint
601
+ ```
602
+
603
+ **Description:**
604
+
605
+ it triggers `lint` GH Action
606
+
607
+ ## unit-tests
608
+
609
+ Conducts unit tests
610
+
611
+ **Example:**
612
+
613
+ ```bash
614
+ $ davinci new-workflow unit-tests
615
+ ```
616
+
617
+ **Description:**
618
+
619
+ it triggers `unit-tests` GH Action
620
+
621
+ ## integration-tests
622
+
623
+ Conducts integration tests in a project using Cypress.
624
+
625
+ **Example:**
626
+
627
+ ```bash
628
+ $ davinci new-workflow integration-tests
629
+ ```
630
+
631
+ **Description:**
632
+
633
+ it triggers `integration-tests` GH Action
634
+
635
+ ## danger
636
+
637
+ Checks if the PR title and commit messages comply with Toptal's standards
638
+
639
+ **Example:**
640
+
641
+ ```bash
642
+ $ davinci new-workflow danger
643
+ ```
644
+
645
+ **Description:**
646
+
647
+ it triggers `danger` GH Action
648
+
649
+ ## deploy-temploy
650
+
651
+ Builds & Deploys application to Temploy
652
+
653
+ **Example:**
654
+
655
+ ```bash
656
+ $ davinci new-workflow deploy-temploy
657
+ ```
658
+
659
+ **Description:**
660
+
661
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
662
+
663
+ **Example of usage:**
664
+
665
+ Write a new comment in PR `@toptal-bot run temploy`
666
+
667
+ ## deploy
668
+
669
+ Performs docker image build and deployment to staging/production environment
670
+
671
+ **Example:**
672
+
673
+ ```bash
674
+ $ davinci new-workflow deploy
675
+ ```
676
+
677
+ **Description:**
678
+
679
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
680
+
681
+ * `Deploy` (davinci-deploy.yml)
682
+ * it's triggered when PR is merged to `master` or `main` branch
683
+ * It builds and pushes a new instance of Docker image to google cloud
684
+ * if `davinci.yml` is present in the root folder:
685
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
686
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
687
+ * `Deploy to staging` (davinci-deploy-staging.yml)
688
+ * Triggers Jenkins job for deployment to staging environment
689
+ * how to trigger the Workflow manually:
690
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
691
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
692
+ * `Deploy to production` (davinci-deploy-production.yml)
693
+ * Triggers Jenkins job for deployment to production environment
694
+ * how to trigger the Workflow manually:
695
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
696
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
697
+
698
+ ## alpha-package
699
+
700
+ Executes script to publish alpha version of package to NPM--
701
+
702
+ **Example:**
703
+
704
+ ```bash
705
+ $ davinci new-workflow alpha-package
706
+ ```
707
+
708
+ **Description:**
709
+
710
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
711
+
712
+ **Example of usage:**
713
+
714
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
715
+
716
+ ## typecheck
717
+
718
+ Checks an App on Typescript issues
719
+
720
+ **Example:**
721
+
722
+ ```bash
723
+ $ davinci new-workflow typecheck
724
+ ```
725
+
726
+ **Description:**
727
+
728
+ it triggers `typecheck` GH Action
729
+
730
+ ## lint
731
+
732
+ Checks an App for lint issues
733
+
734
+ **Example:**
735
+
736
+ ```bash
737
+ $ davinci new-workflow lint
738
+ ```
739
+
740
+ **Description:**
741
+
742
+ it triggers `lint` GH Action
743
+
744
+ ## unit-tests
745
+
746
+ Conducts unit tests
747
+
748
+ **Example:**
749
+
750
+ ```bash
751
+ $ davinci new-workflow unit-tests
752
+ ```
753
+
754
+ **Description:**
755
+
756
+ it triggers `unit-tests` GH Action
757
+
758
+ ## integration-tests
759
+
760
+ Conducts integration tests in a project using Cypress.
761
+
762
+ **Example:**
763
+
764
+ ```bash
765
+ $ davinci new-workflow integration-tests
766
+ ```
767
+
768
+ **Description:**
769
+
770
+ it triggers `integration-tests` GH Action
771
+
772
+ ## danger
773
+
774
+ Checks if the PR title and commit messages comply with Toptal's standards
775
+
776
+ **Example:**
777
+
778
+ ```bash
779
+ $ davinci new-workflow danger
780
+ ```
781
+
782
+ **Description:**
783
+
784
+ it triggers `danger` GH Action
785
+
786
+ ## deploy-temploy
787
+
788
+ Builds & Deploys application to Temploy
789
+
790
+ **Example:**
791
+
792
+ ```bash
793
+ $ davinci new-workflow deploy-temploy
794
+ ```
795
+
796
+ **Description:**
797
+
798
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
799
+
800
+ **Example of usage:**
801
+
802
+ Write a new comment in PR `@toptal-bot run temploy`
803
+
804
+ ## deploy
805
+
806
+ Performs docker image build and deployment to staging/production environment
807
+
808
+ **Example:**
809
+
810
+ ```bash
811
+ $ davinci new-workflow deploy
812
+ ```
813
+
814
+ **Description:**
815
+
816
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
817
+
818
+ * `Deploy` (davinci-deploy.yml)
819
+ * it's triggered when PR is merged to `master` or `main` branch
820
+ * It builds and pushes a new instance of Docker image to google cloud
821
+ * if `davinci.yml` is present in the root folder:
822
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
823
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
824
+ * `Deploy to staging` (davinci-deploy-staging.yml)
825
+ * Triggers Jenkins job for deployment to staging environment
826
+ * how to trigger the Workflow manually:
827
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
828
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
829
+ * `Deploy to production` (davinci-deploy-production.yml)
830
+ * Triggers Jenkins job for deployment to production environment
831
+ * how to trigger the Workflow manually:
832
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
833
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
834
+
835
+ ## alpha-package
836
+
837
+ Executes script to publish alpha version of package to NPM!???!!!
838
+
839
+ **Example:**
840
+
841
+ ```bash
842
+ $ davinci new-workflow alpha-package
843
+ ```
844
+
845
+ **Description:**
846
+
847
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
848
+
849
+ **Example of usage:**
850
+
851
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
852
+
853
+ ## typecheck
854
+
855
+ Checks an App on Typescript issues
856
+
857
+ **Example:**
858
+
859
+ ```bash
860
+ $ davinci new-workflow typecheck
861
+ ```
862
+
863
+ **Description:**
864
+
865
+ it triggers `typecheck` GH Action
866
+
867
+ ## lint
868
+
869
+ Checks an App for lint issues
870
+
871
+ **Example:**
872
+
873
+ ```bash
874
+ $ davinci new-workflow lint
875
+ ```
876
+
877
+ **Description:**
878
+
879
+ it triggers `lint` GH Action
880
+
881
+ ## unit-tests
882
+
883
+ Conducts unit tests
884
+
885
+ **Example:**
886
+
887
+ ```bash
888
+ $ davinci new-workflow unit-tests
889
+ ```
890
+
891
+ **Description:**
892
+
893
+ it triggers `unit-tests` GH Action
894
+
895
+ ## integration-tests
896
+
897
+ Conducts integration tests in a project using Cypress.
898
+
899
+ **Example:**
900
+
901
+ ```bash
902
+ $ davinci new-workflow integration-tests
903
+ ```
904
+
905
+ **Description:**
906
+
907
+ it triggers `integration-tests` GH Action
908
+
909
+ ## danger
910
+
911
+ Checks if the PR title and commit messages comply with Toptal's standards
912
+
913
+ **Example:**
914
+
915
+ ```bash
916
+ $ davinci new-workflow danger
917
+ ```
918
+
919
+ **Description:**
920
+
921
+ it triggers `danger` GH Action
922
+
923
+ ## deploy-temploy
924
+
925
+ Builds & Deploys application to Temploy
926
+
927
+ **Example:**
928
+
929
+ ```bash
930
+ $ davinci new-workflow deploy-temploy
931
+ ```
932
+
933
+ **Description:**
934
+
935
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
936
+
937
+ **Example of usage:**
938
+
939
+ Write a new comment in PR `@toptal-bot run temploy`
940
+
941
+ ## deploy
942
+
943
+ Performs docker image build and deployment to staging/production environment
944
+
945
+ **Example:**
946
+
947
+ ```bash
948
+ $ davinci new-workflow deploy
949
+ ```
950
+
951
+ **Description:**
952
+
953
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
954
+
955
+ * `Deploy` (davinci-deploy.yml)
956
+ * it's triggered when PR is merged to `master` or `main` branch
957
+ * It builds and pushes a new instance of Docker image to google cloud
958
+ * if `davinci.yml` is present in the root folder:
959
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
960
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
961
+ * `Deploy to staging` (davinci-deploy-staging.yml)
962
+ * Triggers Jenkins job for deployment to staging environment
963
+ * how to trigger the Workflow manually:
964
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
965
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
966
+ * `Deploy to production` (davinci-deploy-production.yml)
967
+ * Triggers Jenkins job for deployment to production environment
968
+ * how to trigger the Workflow manually:
969
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
970
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
971
+
972
+ ## alpha-package
973
+
974
+ Executes script to publish alpha version of package to NPM!
975
+
976
+ **Example:**
977
+
978
+ ```bash
979
+ $ davinci new-workflow alpha-package
980
+ ```
981
+
982
+ **Description:**
983
+
984
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
985
+
986
+ **Example of usage:**
987
+
988
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
989
+
990
+ ## typecheck
991
+
992
+ Checks an App on Typescript issues
993
+
994
+ **Example:**
995
+
996
+ ```bash
997
+ $ davinci new-workflow typecheck
998
+ ```
999
+
1000
+ **Description:**
1001
+
1002
+ it triggers `typecheck` GH Action
1003
+
1004
+ ## lint
1005
+
1006
+ Checks an App for lint issues
1007
+
1008
+ **Example:**
1009
+
1010
+ ```bash
1011
+ $ davinci new-workflow lint
1012
+ ```
1013
+
1014
+ **Description:**
1015
+
1016
+ it triggers `lint` GH Action
1017
+
1018
+ ## unit-tests
1019
+
1020
+ Conducts unit tests
1021
+
1022
+ **Example:**
1023
+
1024
+ ```bash
1025
+ $ davinci new-workflow unit-tests
1026
+ ```
1027
+
1028
+ **Description:**
1029
+
1030
+ it triggers `unit-tests` GH Action
1031
+
1032
+ ## integration-tests
1033
+
1034
+ Conducts integration tests in a project using Cypress.
1035
+
1036
+ **Example:**
1037
+
1038
+ ```bash
1039
+ $ davinci new-workflow integration-tests
1040
+ ```
1041
+
1042
+ **Description:**
1043
+
1044
+ it triggers `integration-tests` GH Action
1045
+
1046
+ ## danger
1047
+
1048
+ Checks if the PR title and commit messages comply with Toptal's standards
1049
+
1050
+ **Example:**
1051
+
1052
+ ```bash
1053
+ $ davinci new-workflow danger
1054
+ ```
1055
+
1056
+ **Description:**
1057
+
1058
+ it triggers `danger` GH Action
1059
+
1060
+ ## deploy-temploy
1061
+
1062
+ Builds & Deploys application to Temploy
1063
+
1064
+ **Example:**
1065
+
1066
+ ```bash
1067
+ $ davinci new-workflow deploy-temploy
1068
+ ```
1069
+
1070
+ **Description:**
1071
+
1072
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
1073
+
1074
+ **Example of usage:**
1075
+
1076
+ Write a new comment in PR `@toptal-bot run temploy`
1077
+
1078
+ ## deploy
1079
+
1080
+ Performs docker image build and deployment to staging/production environment
1081
+
1082
+ **Example:**
1083
+
1084
+ ```bash
1085
+ $ davinci new-workflow deploy
1086
+ ```
1087
+
1088
+ **Description:**
1089
+
1090
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
1091
+
1092
+ * `Deploy` (davinci-deploy.yml)
1093
+ * it's triggered when PR is merged to `master` or `main` branch
1094
+ * It builds and pushes a new instance of Docker image to google cloud
1095
+ * if `davinci.yml` is present in the root folder:
1096
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
1097
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
1098
+ * `Deploy to staging` (davinci-deploy-staging.yml)
1099
+ * Triggers Jenkins job for deployment to staging environment
1100
+ * how to trigger the Workflow manually:
1101
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
1102
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
1103
+ * `Deploy to production` (davinci-deploy-production.yml)
1104
+ * Triggers Jenkins job for deployment to production environment
1105
+ * how to trigger the Workflow manually:
1106
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
1107
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
1108
+
1109
+ ## alpha-package
1110
+
1111
+ Executes script to publish alpha version of package to NPM!
1112
+
1113
+ **Example:**
1114
+
1115
+ ```bash
1116
+ $ davinci new-workflow alpha-package
1117
+ ```
1118
+
1119
+ **Description:**
1120
+
1121
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
1122
+
1123
+ **Example of usage:**
1124
+
1125
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
1126
+
1127
+ ## typecheck
1128
+
1129
+ Checks an App on Typescript issues
1130
+
1131
+ **Example:**
1132
+
1133
+ ```bash
1134
+ $ davinci new-workflow typecheck
1135
+ ```
1136
+
1137
+ **Description:**
1138
+
1139
+ it triggers `typecheck` GH Action
1140
+
1141
+ ## lint
1142
+
1143
+ Checks an App for lint issues
1144
+
1145
+ **Example:**
1146
+
1147
+ ```bash
1148
+ $ davinci new-workflow lint
1149
+ ```
1150
+
1151
+ **Description:**
1152
+
1153
+ it triggers `lint` GH Action
1154
+
1155
+ ## unit-tests
1156
+
1157
+ Conducts unit tests
1158
+
1159
+ **Example:**
1160
+
1161
+ ```bash
1162
+ $ davinci new-workflow unit-tests
1163
+ ```
1164
+
1165
+ **Description:**
1166
+
1167
+ it triggers `unit-tests` GH Action
1168
+
1169
+ ## integration-tests
1170
+
1171
+ Conducts integration tests in a project using Cypress.
1172
+
1173
+ **Example:**
1174
+
1175
+ ```bash
1176
+ $ davinci new-workflow integration-tests
1177
+ ```
1178
+
1179
+ **Description:**
1180
+
1181
+ it triggers `integration-tests` GH Action
1182
+
1183
+ ## danger
1184
+
1185
+ Checks if the PR title and commit messages comply with Toptal's standards
1186
+
1187
+ **Example:**
1188
+
1189
+ ```bash
1190
+ $ davinci new-workflow danger
1191
+ ```
1192
+
1193
+ **Description:**
1194
+
1195
+ it triggers `danger` GH Action
1196
+
1197
+ ## deploy-temploy
1198
+
1199
+ Builds & Deploys application to Temploy
1200
+
1201
+ **Example:**
1202
+
1203
+ ```bash
1204
+ $ davinci new-workflow deploy-temploy
1205
+ ```
1206
+
1207
+ **Description:**
1208
+
1209
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
1210
+
1211
+ **Example of usage:**
1212
+
1213
+ Write a new comment in PR `@toptal-bot run temploy`
1214
+
1215
+ ## deploy
1216
+
1217
+ Performs docker image build and deployment to staging/production environment
1218
+
1219
+ **Example:**
1220
+
1221
+ ```bash
1222
+ $ davinci new-workflow deploy
1223
+ ```
1224
+
1225
+ **Description:**
1226
+
1227
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
1228
+
1229
+ * `Deploy` (davinci-deploy.yml)
1230
+ * it's triggered when PR is merged to `master` or `main` branch
1231
+ * It builds and pushes a new instance of Docker image to google cloud
1232
+ * if `davinci.yml` is present in the root folder:
1233
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
1234
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
1235
+ * `Deploy to staging` (davinci-deploy-staging.yml)
1236
+ * Triggers Jenkins job for deployment to staging environment
1237
+ * how to trigger the Workflow manually:
1238
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
1239
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
1240
+ * `Deploy to production` (davinci-deploy-production.yml)
1241
+ * Triggers Jenkins job for deployment to production environment
1242
+ * how to trigger the Workflow manually:
1243
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
1244
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
1245
+
1246
+ ## alpha-package
1247
+
1248
+ Executes script to publish alpha version of package to NPM!!!!!!
1249
+
1250
+ **Example:**
1251
+
1252
+ ```bash
1253
+ $ davinci new-workflow alpha-package
1254
+ ```
1255
+
1256
+ **Description:**
1257
+
1258
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
1259
+
1260
+ **Example of usage:**
1261
+
1262
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
1263
+
1264
+ ## typecheck
1265
+
1266
+ Checks an App on Typescript issues
1267
+
1268
+ **Example:**
1269
+
1270
+ ```bash
1271
+ $ davinci new-workflow typecheck
1272
+ ```
1273
+
1274
+ **Description:**
1275
+
1276
+ it triggers `typecheck` GH Action
1277
+
1278
+ ## lint
1279
+
1280
+ Checks an App for lint issues
1281
+
1282
+ **Example:**
1283
+
1284
+ ```bash
1285
+ $ davinci new-workflow lint
1286
+ ```
1287
+
1288
+ **Description:**
1289
+
1290
+ it triggers `lint` GH Action
1291
+
1292
+ ## unit-tests
1293
+
1294
+ Conducts unit tests
1295
+
1296
+ **Example:**
1297
+
1298
+ ```bash
1299
+ $ davinci new-workflow unit-tests
1300
+ ```
1301
+
1302
+ **Description:**
1303
+
1304
+ it triggers `unit-tests` GH Action
1305
+
1306
+ ## integration-tests
1307
+
1308
+ Conducts integration tests in a project using Cypress.
1309
+
1310
+ **Example:**
1311
+
1312
+ ```bash
1313
+ $ davinci new-workflow integration-tests
1314
+ ```
1315
+
1316
+ **Description:**
1317
+
1318
+ it triggers `integration-tests` GH Action
1319
+
1320
+ ## danger
1321
+
1322
+ Checks if the PR title and commit messages comply with Toptal's standards
1323
+
1324
+ **Example:**
1325
+
1326
+ ```bash
1327
+ $ davinci new-workflow danger
1328
+ ```
1329
+
1330
+ **Description:**
1331
+
1332
+ it triggers `danger` GH Action
1333
+
1334
+ ## deploy-temploy
1335
+
1336
+ Builds & Deploys application to Temploy
1337
+
1338
+ **Example:**
1339
+
1340
+ ```bash
1341
+ $ davinci new-workflow deploy-temploy
1342
+ ```
1343
+
1344
+ **Description:**
1345
+
1346
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
1347
+
1348
+ **Example of usage:**
1349
+
1350
+ Write a new comment in PR `@toptal-bot run temploy`
1351
+
1352
+ ## deploy
1353
+
1354
+ Performs docker image build and deployment to staging/production environment
1355
+
1356
+ **Example:**
1357
+
1358
+ ```bash
1359
+ $ davinci new-workflow deploy
1360
+ ```
1361
+
1362
+ **Description:**
1363
+
1364
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
1365
+
1366
+ * `Deploy` (davinci-deploy.yml)
1367
+ * it's triggered when PR is merged to `master` or `main` branch
1368
+ * It builds and pushes a new instance of Docker image to google cloud
1369
+ * if `davinci.yml` is present in the root folder:
1370
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
1371
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
1372
+ * `Deploy to staging` (davinci-deploy-staging.yml)
1373
+ * Triggers Jenkins job for deployment to staging environment
1374
+ * how to trigger the Workflow manually:
1375
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
1376
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
1377
+ * `Deploy to production` (davinci-deploy-production.yml)
1378
+ * Triggers Jenkins job for deployment to production environment
1379
+ * how to trigger the Workflow manually:
1380
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
1381
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
1382
+
1383
+ ## alpha-package
1384
+
1385
+ Executes script to publish alpha version of package to NPM!!!!!!
1386
+
1387
+ **Example:**
1388
+
1389
+ ```bash
1390
+ $ davinci new-workflow alpha-package
1391
+ ```
1392
+
1393
+ **Description:**
1394
+
1395
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
1396
+
1397
+ **Example of usage:**
1398
+
1399
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
1400
+
1401
+ ## typecheck
1402
+
1403
+ Checks an App on Typescript issues
1404
+
1405
+ **Example:**
1406
+
1407
+ ```bash
1408
+ $ davinci new-workflow typecheck
1409
+ ```
1410
+
1411
+ **Description:**
1412
+
1413
+ it triggers `typecheck` GH Action
1414
+
1415
+ ## lint
1416
+
1417
+ Checks an App for lint issues
1418
+
1419
+ **Example:**
1420
+
1421
+ ```bash
1422
+ $ davinci new-workflow lint
1423
+ ```
1424
+
1425
+ **Description:**
1426
+
1427
+ it triggers `lint` GH Action
1428
+
1429
+ ## unit-tests
1430
+
1431
+ Conducts unit tests
1432
+
1433
+ **Example:**
1434
+
1435
+ ```bash
1436
+ $ davinci new-workflow unit-tests
1437
+ ```
1438
+
1439
+ **Description:**
1440
+
1441
+ it triggers `unit-tests` GH Action
1442
+
1443
+ ## integration-tests
1444
+
1445
+ Conducts integration tests in a project using Cypress.
1446
+
1447
+ **Example:**
1448
+
1449
+ ```bash
1450
+ $ davinci new-workflow integration-tests
1451
+ ```
1452
+
1453
+ **Description:**
1454
+
1455
+ it triggers `integration-tests` GH Action
1456
+
1457
+ ## danger
1458
+
1459
+ Checks if the PR title and commit messages comply with Toptal's standards
1460
+
1461
+ **Example:**
1462
+
1463
+ ```bash
1464
+ $ davinci new-workflow danger
1465
+ ```
1466
+
1467
+ **Description:**
1468
+
1469
+ it triggers `danger` GH Action
1470
+
1471
+ ## deploy-temploy
1472
+
1473
+ Builds & Deploys application to Temploy
1474
+
1475
+ **Example:**
1476
+
1477
+ ```bash
1478
+ $ davinci new-workflow deploy-temploy
1479
+ ```
1480
+
1481
+ **Description:**
1482
+
1483
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
1484
+
1485
+ **Example of usage:**
1486
+
1487
+ Write a new comment in PR `@toptal-bot run temploy`
1488
+
1489
+ ## deploy
1490
+
1491
+ Performs docker image build and deployment to staging/production environment
1492
+
1493
+ **Example:**
1494
+
1495
+ ```bash
1496
+ $ davinci new-workflow deploy
1497
+ ```
1498
+
1499
+ **Description:**
1500
+
1501
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
1502
+
1503
+ * `Deploy` (davinci-deploy.yml)
1504
+ * it's triggered when PR is merged to `master` or `main` branch
1505
+ * It builds and pushes a new instance of Docker image to google cloud
1506
+ * if `davinci.yml` is present in the root folder:
1507
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
1508
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
1509
+ * `Deploy to staging` (davinci-deploy-staging.yml)
1510
+ * Triggers Jenkins job for deployment to staging environment
1511
+ * how to trigger the Workflow manually:
1512
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
1513
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
1514
+ * `Deploy to production` (davinci-deploy-production.yml)
1515
+ * Triggers Jenkins job for deployment to production environment
1516
+ * how to trigger the Workflow manually:
1517
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
1518
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
1519
+
1520
+ ## alpha-package
1521
+
1522
+ Executes script to publish alpha version of package to NPM!
1523
+
1524
+ **Example:**
1525
+
1526
+ ```bash
1527
+ $ davinci new-workflow alpha-package
1528
+ ```
1529
+
1530
+ **Description:**
1531
+
1532
+ it triggers [build-publish-alpha-package](https://github.com/toptal/davinci-github-actions/tree/master/build-publish-alpha-package) GH Action.
1533
+
1534
+ **Example of usage:**
1535
+
1536
+ Write a new comment in PR `@toptal-bot run package:alpha-release`
1537
+
1538
+ ## typecheck
1539
+
1540
+ Checks an App on Typescript issues
1541
+
1542
+ **Example:**
1543
+
1544
+ ```bash
1545
+ $ davinci new-workflow typecheck
1546
+ ```
1547
+
1548
+ **Description:**
1549
+
1550
+ it triggers `typecheck` GH Action
1551
+
1552
+ ## lint
1553
+
1554
+ Checks an App for lint issues
1555
+
1556
+ **Example:**
1557
+
1558
+ ```bash
1559
+ $ davinci new-workflow lint
1560
+ ```
1561
+
1562
+ **Description:**
1563
+
1564
+ it triggers `lint` GH Action
1565
+
1566
+ ## unit-tests
1567
+
1568
+ Conducts unit tests
1569
+
1570
+ **Example:**
1571
+
1572
+ ```bash
1573
+ $ davinci new-workflow unit-tests
1574
+ ```
1575
+
1576
+ **Description:**
1577
+
1578
+ it triggers `unit-tests` GH Action
1579
+
1580
+ ## integration-tests
1581
+
1582
+ Conducts integration tests in a project using Cypress.
1583
+
1584
+ **Example:**
1585
+
1586
+ ```bash
1587
+ $ davinci new-workflow integration-tests
1588
+ ```
1589
+
1590
+ **Description:**
1591
+
1592
+ it triggers `integration-tests` GH Action
1593
+
1594
+ ## danger
1595
+
1596
+ Checks if the PR title and commit messages comply with Toptal's standards
1597
+
1598
+ **Example:**
1599
+
1600
+ ```bash
1601
+ $ davinci new-workflow danger
1602
+ ```
1603
+
1604
+ **Description:**
1605
+
1606
+ it triggers `danger` GH Action
1607
+
1608
+ ## deploy-temploy
1609
+
1610
+ Builds & Deploys application to Temploy
1611
+
1612
+ **Example:**
1613
+
1614
+ ```bash
1615
+ $ davinci new-workflow deploy-temploy
1616
+ ```
1617
+
1618
+ **Description:**
1619
+
1620
+ it creates a new instance of Docker image, pushes it to cloud and triggers an appropriate Jenkins job to deploy the image to temploy.
1621
+
1622
+ **Example of usage:**
1623
+
1624
+ Write a new comment in PR `@toptal-bot run temploy`
1625
+
1626
+ ## deploy
1627
+
1628
+ Performs docker image build and deployment to staging/production environment
1629
+
1630
+ **Example:**
1631
+
1632
+ ```bash
1633
+ $ davinci new-workflow deploy
1634
+ ```
1635
+
1636
+ **Description:**
1637
+
1638
+ performs docker image build and deployment to staging/production environment. Consists of three Workflows:
1639
+
1640
+ * `Deploy` (davinci-deploy.yml)
1641
+ * it's triggered when PR is merged to `master` or `main` branch
1642
+ * It builds and pushes a new instance of Docker image to google cloud
1643
+ * if `davinci.yml` is present in the root folder:
1644
+ * and `deploy_staging` key is set to **true** then triggers `Deploy to Staging` GH Workflow
1645
+ * and `deploy` key is set to **true** then triggers `Deploy to Production` GH Workflow
1646
+ * `Deploy to staging` (davinci-deploy-staging.yml)
1647
+ * Triggers Jenkins job for deployment to staging environment
1648
+ * how to trigger the Workflow manually:
1649
+ * add a new comment: `@toptal-bot run deploy-staging` in a PR. It will trigger a new GH Workflow. The latest commit in the PR branch will be taken to build a docker image.
1650
+ * In the `actions` tab, choose `Deploy to Staging` GH Workflow and provide a commit SHA
1651
+ * `Deploy to production` (davinci-deploy-production.yml)
1652
+ * Triggers Jenkins job for deployment to production environment
1653
+ * how to trigger the Workflow manually:
1654
+ * In the `actions` tab, choose `Deploy to Production` GH Workflow and provide a commit SHA
1655
+ * Find out more about how deployment works in [confluence](https://toptal-core.atlassian.net/l/c/ZN2K1f0r)
1656
+
52
1657
  ## Alias
53
1658
 
54
1659
  In all the commands you can use `davinci-workflow` directly if needed, instead of `davinci workflow`. This is not a recommended way to use `davinci`, but in very rare cases it might be useful.
55
-