You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: __tests__/shared/utils/__snapshots__/markdown.js.snap
+24-39
Original file line number
Diff line number
Diff line change
@@ -796,9 +796,6 @@ Array [
796
796
>
797
797
>
798
798
</span>
799
-
<span
800
-
className="bash"
801
-
/>
802
799
</code>
803
800
characters for blockquoting. If you’re
804
801
<br />
@@ -813,9 +810,6 @@ Array [
813
810
>
814
811
>
815
812
</span>
816
-
<span
817
-
className="bash"
818
-
/>
819
813
</code>
820
814
before every line:
821
815
</p>,
@@ -841,9 +835,6 @@ Array [
841
835
>
842
836
>
843
837
</span>
844
-
<span
845
-
className="bash"
846
-
/>
847
838
</code>
848
839
before the first
849
840
<br />
@@ -875,9 +866,6 @@ Array [
875
866
>
876
867
>
877
868
</span>
878
-
<span
879
-
className="bash"
880
-
/>
881
869
</code>
882
870
:
883
871
</p>,
@@ -1182,9 +1170,6 @@ Array [
1182
1170
>
1183
1171
>
1184
1172
</span>
1185
-
<span
1186
-
className="bash"
1187
-
/>
1188
1173
</code>
1189
1174
<br />
1190
1175
delimiters need to be indented:
@@ -1297,9 +1282,6 @@ end tell
1297
1282
>
1298
1283
>
1299
1284
</span>
1300
-
<span
1301
-
className="bash"
1302
-
/>
1303
1285
</code>
1304
1286
)
1305
1287
<br />
@@ -1429,7 +1411,7 @@ end tell
1429
1411
) and underscores (
1430
1412
<code>
1431
1413
<span
1432
-
className="hljs-keyword"
1414
+
className="hljs-literal"
1433
1415
>
1434
1416
_
1435
1417
</span>
@@ -1447,7 +1429,7 @@ end tell
1447
1429
or
1448
1430
<code>
1449
1431
<span
1450
-
className="hljs-keyword"
1432
+
className="hljs-literal"
1451
1433
>
1452
1434
_
1453
1435
</span>
@@ -1473,7 +1455,7 @@ end tell
1473
1455
's or
1474
1456
<code>
1475
1457
<span
1476
-
className="hljs-keyword"
1458
+
className="hljs-literal"
1477
1459
>
1478
1460
_
1479
1461
</span>
@@ -2198,39 +2180,42 @@ Array [
2198
2180
Ad amet irure est magna id mollit Lorem in do duis enim. Excepteur velit nisi magna ea pariatur pariatur ullamco fugiat deserunt sint non sint. Duis duis est
2199
2181
<code>
2200
2182
<span
2201
-
className="hljs-selector-tag"
2183
+
className="hljs-built_in"
2202
2184
>
2203
2185
code
2204
2186
</span>
2205
-
2187
+
in
2206
2188
<span
2207
-
className="hljs-keyword"
2189
+
className="hljs-built_in"
2208
2190
>
2209
-
in
2191
+
text
2210
2192
</span>
2211
-
text
2212
2193
</code>
2213
2194
velit velit aute culpa ex quis pariatur pariatur laborum aute pariatur duis tempor sunt ad. Irure magna voluptate dolore consectetur consectetur irure esse. Anim magna
2214
2195
<code>
2215
-
<
2216
-
<span
2217
-
className="hljs-keyword"
2218
-
>
2219
-
strong
2220
-
</span>
2221
-
>
2222
2196
<span
2223
-
className="hljs-keyword"
2197
+
className="hljs-tag"
2224
2198
>
2225
-
in
2199
+
<
2200
+
<span
2201
+
className="hljs-name"
2202
+
>
2203
+
strong
2204
+
</span>
2205
+
>
2226
2206
</span>
2227
-
culpa qui officia</
2207
+
in culpa qui officia
2228
2208
<span
2229
-
className="hljs-keyword"
2209
+
className="hljs-tag"
2230
2210
>
2231
-
strong
2211
+
</
2212
+
<span
2213
+
className="hljs-name"
2214
+
>
2215
+
strong
2216
+
</span>
2217
+
>
2232
2218
</span>
2233
-
>
2234
2219
</code>
2235
2220
dolor eiusmod esse amet aute cupidatat aliqua do id voluptate cupidatat reprehenderit amet labore deserunt.
This document describes the Topcoder issue/feature release process using TCX. This is a guide for co-pilots, QA, architects and community members. Co-pilot is the driver of the whole process from opening a ticket to the deployment.
3
+
4
+
## Code Phase
5
+
6
+
1. Create a branch from the `master` and name it as `hot-fix-fixtitle` or `feature-featuretitle`
7
+
2. Co-pilot will prepare and launch a ticket
8
+
9
+
a. Add Prize in the issue title [$SOMEAMOUT]
10
+
11
+
b. Mention PR branch, this branch should be always in sync with master or newly created as mentioned in 1
12
+
13
+
c. Add this to instruction that all the PR should pass `npm test`
14
+
15
+
d. Change label to `tcx_OpenForPickup`
16
+
17
+
e. Tag the community @topcoder-platform/tcxcommunity@topcoder-platform/topcodercompetitors
18
+
3. A competitor assings a ticket to self (`tcx_Assigned`), writes the code for the fix
19
+
4. Competitor, PR to the branch (submission) and they should change the label to `tcx_ReadyForReview`
20
+
21
+
## Review Phase
22
+
23
+
4. Co-pilot will review the code, based on review change the label to
24
+
25
+
a. `tcx_Feedback` - Feedback should be mentioned in the comments section, this may lead to asking for patch PR
26
+
27
+
b. `Code Review Passed` and `tcx_FixAccepted`- This goes to QA Deployment Phase
28
+
29
+
c. `Code Review Failed` - This goes to 1
30
+
31
+
## QA Deployment Phase
32
+
33
+
5. Based on the label `Code Review Passed`, co-pilot should request deployment to the architect. Based on whatever testing deployment environment is available to code will be deployed.
34
+
35
+
6. Once deployed on the environment co-pilot will change the label to `Ready for QA` and will inform the QA team on #community-app slack channel.
36
+
37
+
7. Based on QA feedback label should be `QA Pass` or `QA Fail`
38
+
39
+
8.`QA Fail` label will go to **Review Phase** again
40
+
41
+
9.`QA Pass` label is a candidate for production deployment
42
+
43
+
10. Co-pilot will create PR to `fix-branch > develop` branch
44
+
45
+
11. An architect will merge PR and ask for smoke testing to the QA team
46
+
47
+
12. If smoke testing goes well, co-pilot create PR to `develop > master`
48
+
49
+
13. It takes around 20 mins for deployment on any deployment.
50
+
51
+
14. QA team will verify the post-production issue fix.
52
+
53
+
15. If post-production test passes QA team will change the label to `Prod QA Pass`, Co-pilot will close this ticket
54
+
55
+
17. If post-production test fails QA team will change the label to `Prod QA Failed`
0 commit comments