99 </p >
1010
1111 <p >
12- An enterprise react template application showcasing - Testing strategies, Global state management, middleware support, a network layer, component library integration, localization, PWA support, route configuration, lazy loading, and Continuous integration & deployment.
12+ An enterprise electron template application showcasing - Testing strategies, Global state management, middleware support, a network layer, component library integration, localization, PWA support, route configuration, lazy loading, and Continuous integration & deployment.
1313 </p >
1414
1515---
@@ -33,7 +33,7 @@ An enterprise react template application showcasing - Testing strategies, Global
3333
3434</div >
3535
36- ![ React GraphQL TS Template CD] ( https://github.com/wednesday-solutions/react-graphql-ts-template/workflows/React%20GraphQL%20TypeScript%20Template%20CD/badge.svg )
36+ ![ ELECTRON REACT TS Template CD] ( https://github.com/wednesday-solutions/react-graphql-ts-template/workflows/React%20GraphQL%20TypeScript%20Template%20CD/badge.svg )
3737
3838<div >
3939<img src =' ./badges/badge-statements.svg ' height =" 20 " />
@@ -48,10 +48,20 @@ An enterprise react template application showcasing - Testing strategies, Global
4848
4949- Install dependencies using ` yarn install `
5050
51- - Start the dev server using ` yarn start `
51+ - Start the electron dev server using ` yarn run electron:start `
52+
53+ - Package the app for production using ` yarn run electron:package `
5254
5355- Go through the other scripts in ` package.json `
5456
57+ ## Electron Configuration
58+
59+ - Electron configuration using [ main.js] ( https://www.electronjs.org/docs/latest/tutorial/examples )
60+
61+ Take a look at the following files
62+
63+ - [ main/main.js] ( main/main.js )
64+
5565## TypeScript Configuration
5666
5767- Typescript Configuration using [ tsconfig.json] ( https://www.typescriptlang.org/docs/handbook/tsconfig-json.html )
@@ -189,6 +199,20 @@ An enterprise react template application showcasing - Testing strategies, Global
189199 - [ .github/workflows/ci.yml] ( .github/workflows/ci.yml )
190200 - [ .github/workflows/cd.yml] ( .github/workflows/cd.yml )
191201
202+ ## Auto release
203+
204+ - Each push into ` dev ` branch will produce a alpha release
205+ - Each push into ` staging ` branch will produce a beta release
206+ - Each push into ` master ` branch will produce a prod release
207+
208+ These releases will also have the respective packaged electron app in it assets.
209+
210+ Take a look at the following files
211+
212+ - [ .github/workflows/cd-alpha-release.yml] ( .github/workflows/cd-alpha-release.yml )
213+ - [ .github/workflows/cd-beta-release.yml] ( .github/workflows/cd-beta-release.yml )
214+ - [ .github/workflows/cd-latest-release.yml] ( .github/workflows/cd-latest-release.yml )
215+
192216## Testing using @testing-library/react
193217
194218- Testing is done using the @testing-library/react .
@@ -265,13 +289,3 @@ Where `type` is one of the following:
265289 Where ` flags ` is an optional comma-separated list of one or more of the following (must be surrounded in square brackets):
266290- ` breaking ` : alters ` type ` to be a breaking change
267291 And ` category ` can be anything of your choice. If you use a type not found in the list (but it still follows the same format of the message), it'll be grouped under ` other ` .
268-
269- ## Auto release
270-
271- - Each push into ` qa ` branch will produce a beta release
272- - Each push into ` master ` branch will produce a prod release
273-
274- Take a look at the following files
275-
276- - [ .github/workflows/beta-release.yml] ( .github/workflows/beta-release.yml )
277- - [ .github/workflows/prod-release.yml] ( .github/workflows/prod-release.yml )
0 commit comments