wp-advads 1.0.12 → 1.0.13

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.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/src/commands/setup/create-plugin.js +4 -0
  3. package/template/.github/pull_request_template.md +52 -0
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "type": "module",
3
3
  "name": "wp-advads",
4
- "version": "1.0.12",
4
+ "version": "1.0.13",
5
5
  "description": "Create a Advanced Ads wordPress plugin eco system.",
6
6
  "author": {
7
7
  "name": "Shakeeb Ahmed",
package/src/commands/setup/create-plugin.js CHANGED
@@ -80,6 +80,10 @@ function copyToolFiles(next) {
80
80
  pluginData.template + '/tools',
81
81
  pluginData.folder + '/tools',
82
82
  )
83
+ fs.copySync(
84
+ pluginData.template + '/.github',
85
+ pluginData.folder + '/.github',
86
+ )
83
87
 
84
88
  msgSuccessOnSameLine('Tool files copied')
85
89
  next()
package/template/.github/pull_request_template.md ADDED
@@ -0,0 +1,52 @@
1
+ ## Description
2
+
3
+ Please include a summary of the change and which issue is fixed. Provide a clear explanation of the motivation and context behind the change, including how it aligns with project goals.
4
+
5
+ ## Issue ticket number and link
6
+ Related to: #[Issue Number]
7
+ Closes: #[Issue Number]
8
+
9
+ ## How Has This Been Tested?
10
+
11
+ Describe the tests that were conducted to verify the changes. Include instructions for reproducing the tests and any relevant details about the test configuration.
12
+
13
+ - [ ] Automated Test A (Purpose of Test A)
14
+ - [ ] Automated Test B (Purpose of Test B)
15
+ - [ ] Manual Test A (Purpose of Test A)
16
+ - [ ] Manual Test B (Purpose of Test B)
17
+
18
+ ## Checklist:
19
+
20
+ ### Developer -> Code Review:
21
+ - [ ] PR title is clear and descriptive
22
+ - [ ] Code follows the style guidelines of this project
23
+ - [ ] I have performed a self-review of my own code
24
+ - [ ] Code is easily understandable and well-documented
25
+ - [ ] Request a code review from a peer or senior developer
26
+
27
+ ### Developer -> Testing:
28
+ - [ ] My changes generate no new warnings
29
+ - [ ] New and existing unit tests pass locally with my changes
30
+ - [ ] I have added tests that prove my fix is effective or that my feature works
31
+
32
+ ### Developer -> Documentation:
33
+ - [ ] I have made corresponding changelogs
34
+ - [ ] (Optional) Update relevant documentation, such as API endpoints, configuration changes, or user guides
35
+
36
+ ### Developer -> Dependencies:
37
+ - [ ] Ensure your changes do not introduce new external dependencies without proper justification
38
+
39
+ ### Assignee -> Review:
40
+ - [ ] Ensure the PR aligns with the original user story or feature requirement
41
+ - [ ] Review the code changes to ensure they match the product's design and functionality expectations
42
+
43
+ ### Assignee -> Testing:
44
+ - [ ] Conduct user acceptance testing to validate that the changes meet the user's needs
45
+ - [ ] Verify that the feature works as expected and doesn't introduce regressions
46
+ - [ ] No issues have been found on the staging environment
47
+ - [ ] PR reviewer has approved the release
48
+ - [ ] Final changelog has been determined/approved
49
+
50
+ ## Further comments
51
+
52
+ If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...