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: README.md
+16-12Lines changed: 16 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,12 +21,15 @@
21
21
22
22
## How to start development
23
23
24
-
This plugin does not include build assets and PHP-dependencies. Therefore, after loading that repository via Composer or git checkout you have to install them.
24
+
> [!NOTE]
25
+
> The `master` branch contains a production-ready plugin with pre-built assets, but development happens on other branches.
25
26
26
-
**With Yarn:**
27
+
For development, clone the repository (which uses the default development branch) and run the build process to generate the required assets and install PHP dependencies before you begin coding:
27
28
28
29
```shell
29
-
yarn install && yarn build
30
+
cd google-tag-manager
31
+
composer install
32
+
npm install && npm run build
30
33
```
31
34
32
35
## Testing & Quality
@@ -47,20 +50,21 @@ vendor/bin/phpunit
47
50
48
51
## How to create a release
49
52
50
-
To create a release go to the `<target>-built` branch and create the tag and the release.
53
+
To create a release go to the `<target>` branch and create the tag and the release.
51
54
52
55
**Example 1: A change is going to be added to `master` branch.**
53
56
54
-
A developer makes a PR to `master` branch adding a feature.
55
-
Once it gets merged a build & push workflow will be triggered.
56
-
[bot] This workflow will create a build and push it to `master-built` branch.
57
-
[human] Then create a tag on `master-built` and then a release.
57
+
-A developer makes a PR to `dev/master` branch adding a feature.
58
+
-Once it gets merged, a maintainer triggers the `Build and distribute`workflow providing the version number to be released.
59
+
-[bot] This workflow will create a build and push it to `master` branch.
60
+
-[human] Then create a tag on `master` and then a release.
58
61
59
62
**Example 2: A change is going to be added to `1.x` branch.**
60
-
A developer makes a PR to `1.x` branch adding a feature.
61
-
Once it gets merged a build & push workflow will be triggered.
62
-
[bot] This workflow will create a build and push it to `1.x-built` branch.
63
-
[human] Then create a tag on `1.x-built` and then a release.
63
+
64
+
- A developer makes a PR to `dev/1.x` branch adding a feature.
65
+
- Once it gets merged, a maintainer triggers the `Build and distribute` workflow providing the version number to be released.
66
+
-[bot] This workflow will create a build and push it to `1.x` branch.
67
+
-[human] Then create a tag on `1.x` and then a release.
0 commit comments