projen-modules 3.0.2__tar.gz → 3.1.0__tar.gz

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.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: projen_modules
3
- Version: 3.0.2
3
+ Version: 3.1.0
4
4
  Summary: A collection of projen modules
5
5
  Home-page: https://github.com/daveshepherd/projen-modules.git
6
6
  Author: Dave Shepherd<dave.shepherd@endor.me.uk>
@@ -55,6 +55,38 @@ Types of testing:
55
55
  * Snapshot - projen project outputs are stored as a snapshot in the corresponding `__snapshots__` directory. When the project changes then it is expected that these snapshots change too and should be reviewed committed alongside the project.
56
56
  * Unit tests - these assert on specific functionality of the project and should be written for any new functionality added.
57
57
 
58
+ ## GitHub Configuration
59
+
60
+ All pull requests are merged by the [Mergify](https://mergify.com) merge queue, configured in `.mergify.yml`. Once a pull request's checks pass, Mergify queues it, brings it up to date with the default branch, waits for the checks again and squash merges it. Draft pull requests and those labelled `do-not-merge` are not merged.
61
+
62
+ The repository must be configured as below so that nothing can be merged without going through the queue.
63
+
64
+ ### Mergify
65
+
66
+ Install the [Mergify GitHub App](https://github.com/apps/mergify) and give it access to this repository.
67
+
68
+ ### Pull request settings
69
+
70
+ In **Settings → General → Pull Requests**:
71
+
72
+ * Allow squash merging only (untick merge commits and rebase merging), matching the queue's merge method.
73
+ * Untick **Allow auto-merge**, because GitHub's own auto-merge merges outside the queue.
74
+ * Tick **Automatically delete head branches**.
75
+
76
+ ### Branch ruleset
77
+
78
+ In **Settings → Rules → Rulesets**, create a branch ruleset with enforcement **Active** that targets the default branch, and set:
79
+
80
+ * **Bypass list**: the **Mergify** app only, in **Exempt** mode. Do not add admins or other roles, as anyone on this list can merge without the queue.
81
+ * **Restrict updates**: only bypass actors can update the branch, so pull requests cannot be merged from the GitHub UI or CLI and commits cannot be pushed directly.
82
+ * **Restrict deletions** and **Block force pushes**.
83
+ * **Require a pull request before merging**, with 0 required approvals.
84
+ * **Require status checks to pass**, listing the checks that `.mergify.yml` waits for: `build`, `package-js`, `package-python`. Leave **Require branches to be up to date before merging** unticked, as the queue already updates and retests each pull request.
85
+
86
+ Do not enable GitHub's own **Require merge queue** rule, as it competes with Mergify.
87
+
88
+ If the queue is unavailable and a change has to be merged, add yourself to the bypass list temporarily and remove yourself afterwards.
89
+
58
90
  ## Creating a New Project
59
91
 
60
92
  ```
@@ -27,6 +27,38 @@ Types of testing:
27
27
  * Snapshot - projen project outputs are stored as a snapshot in the corresponding `__snapshots__` directory. When the project changes then it is expected that these snapshots change too and should be reviewed committed alongside the project.
28
28
  * Unit tests - these assert on specific functionality of the project and should be written for any new functionality added.
29
29
 
30
+ ## GitHub Configuration
31
+
32
+ All pull requests are merged by the [Mergify](https://mergify.com) merge queue, configured in `.mergify.yml`. Once a pull request's checks pass, Mergify queues it, brings it up to date with the default branch, waits for the checks again and squash merges it. Draft pull requests and those labelled `do-not-merge` are not merged.
33
+
34
+ The repository must be configured as below so that nothing can be merged without going through the queue.
35
+
36
+ ### Mergify
37
+
38
+ Install the [Mergify GitHub App](https://github.com/apps/mergify) and give it access to this repository.
39
+
40
+ ### Pull request settings
41
+
42
+ In **Settings → General → Pull Requests**:
43
+
44
+ * Allow squash merging only (untick merge commits and rebase merging), matching the queue's merge method.
45
+ * Untick **Allow auto-merge**, because GitHub's own auto-merge merges outside the queue.
46
+ * Tick **Automatically delete head branches**.
47
+
48
+ ### Branch ruleset
49
+
50
+ In **Settings → Rules → Rulesets**, create a branch ruleset with enforcement **Active** that targets the default branch, and set:
51
+
52
+ * **Bypass list**: the **Mergify** app only, in **Exempt** mode. Do not add admins or other roles, as anyone on this list can merge without the queue.
53
+ * **Restrict updates**: only bypass actors can update the branch, so pull requests cannot be merged from the GitHub UI or CLI and commits cannot be pushed directly.
54
+ * **Restrict deletions** and **Block force pushes**.
55
+ * **Require a pull request before merging**, with 0 required approvals.
56
+ * **Require status checks to pass**, listing the checks that `.mergify.yml` waits for: `build`, `package-js`, `package-python`. Leave **Require branches to be up to date before merging** unticked, as the queue already updates and retests each pull request.
57
+
58
+ Do not enable GitHub's own **Require merge queue** rule, as it competes with Mergify.
59
+
60
+ If the queue is unavailable and a change has to be merged, add yourself to the bypass list temporarily and remove yourself afterwards.
61
+
30
62
  ## Creating a New Project
31
63
 
32
64
  ```
@@ -5,7 +5,7 @@ kwargs = json.loads(
5
5
  """
6
6
  {
7
7
  "name": "projen_modules",
8
- "version": "3.0.2",
8
+ "version": "3.1.0",
9
9
  "description": "A collection of projen modules",
10
10
  "license": "Apache-2.0",
11
11
  "url": "https://github.com/daveshepherd/projen-modules.git",
@@ -26,7 +26,7 @@ kwargs = json.loads(
26
26
  ],
27
27
  "package_data": {
28
28
  "projen_modules._jsii": [
29
- "projen-modules@3.0.2.jsii.tgz"
29
+ "projen-modules@3.1.0.jsii.tgz"
30
30
  ],
31
31
  "projen_modules": [
32
32
  "py.typed"
@@ -28,6 +28,38 @@ Types of testing:
28
28
  * Snapshot - projen project outputs are stored as a snapshot in the corresponding `__snapshots__` directory. When the project changes then it is expected that these snapshots change too and should be reviewed committed alongside the project.
29
29
  * Unit tests - these assert on specific functionality of the project and should be written for any new functionality added.
30
30
 
31
+ ## GitHub Configuration
32
+
33
+ All pull requests are merged by the [Mergify](https://mergify.com) merge queue, configured in `.mergify.yml`. Once a pull request's checks pass, Mergify queues it, brings it up to date with the default branch, waits for the checks again and squash merges it. Draft pull requests and those labelled `do-not-merge` are not merged.
34
+
35
+ The repository must be configured as below so that nothing can be merged without going through the queue.
36
+
37
+ ### Mergify
38
+
39
+ Install the [Mergify GitHub App](https://github.com/apps/mergify) and give it access to this repository.
40
+
41
+ ### Pull request settings
42
+
43
+ In **Settings → General → Pull Requests**:
44
+
45
+ * Allow squash merging only (untick merge commits and rebase merging), matching the queue's merge method.
46
+ * Untick **Allow auto-merge**, because GitHub's own auto-merge merges outside the queue.
47
+ * Tick **Automatically delete head branches**.
48
+
49
+ ### Branch ruleset
50
+
51
+ In **Settings → Rules → Rulesets**, create a branch ruleset with enforcement **Active** that targets the default branch, and set:
52
+
53
+ * **Bypass list**: the **Mergify** app only, in **Exempt** mode. Do not add admins or other roles, as anyone on this list can merge without the queue.
54
+ * **Restrict updates**: only bypass actors can update the branch, so pull requests cannot be merged from the GitHub UI or CLI and commits cannot be pushed directly.
55
+ * **Restrict deletions** and **Block force pushes**.
56
+ * **Require a pull request before merging**, with 0 required approvals.
57
+ * **Require status checks to pass**, listing the checks that `.mergify.yml` waits for: `build`, `package-js`, `package-python`. Leave **Require branches to be up to date before merging** unticked, as the queue already updates and retests each pull request.
58
+
59
+ Do not enable GitHub's own **Require merge queue** rule, as it competes with Mergify.
60
+
61
+ If the queue is unavailable and a change has to be merged, add yourself to the bypass list temporarily and remove yourself afterwards.
62
+
31
63
  ## Creating a New Project
32
64
 
33
65
  ```
@@ -11703,6 +11735,11 @@ class PythonPackage(
11703
11735
 
11704
11736
  jsii.create(self.__class__, self, [options])
11705
11737
 
11738
+ @builtins.property
11739
+ @jsii.member(jsii_name="autoMerge")
11740
+ def auto_merge(self) -> typing.Optional["_projen_github_04054675.AutoMerge"]:
11741
+ return typing.cast(typing.Optional["_projen_github_04054675.AutoMerge"], jsii.get(self, "autoMerge"))
11742
+
11706
11743
  @builtins.property
11707
11744
  @jsii.member(jsii_name="readme")
11708
11745
  def readme(self) -> "Readme":
@@ -18,7 +18,7 @@ import constructs._jsii
18
18
  import projen._jsii
19
19
 
20
20
  __jsii_assembly__ = jsii.JSIIAssembly.load(
21
- "projen-modules", "3.0.2", __name__[0:-6], "projen-modules@3.0.2.jsii.tgz"
21
+ "projen-modules", "3.1.0", __name__[0:-6], "projen-modules@3.1.0.jsii.tgz"
22
22
  )
23
23
 
24
24
  __all__ = [
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: projen_modules
3
- Version: 3.0.2
3
+ Version: 3.1.0
4
4
  Summary: A collection of projen modules
5
5
  Home-page: https://github.com/daveshepherd/projen-modules.git
6
6
  Author: Dave Shepherd<dave.shepherd@endor.me.uk>
@@ -55,6 +55,38 @@ Types of testing:
55
55
  * Snapshot - projen project outputs are stored as a snapshot in the corresponding `__snapshots__` directory. When the project changes then it is expected that these snapshots change too and should be reviewed committed alongside the project.
56
56
  * Unit tests - these assert on specific functionality of the project and should be written for any new functionality added.
57
57
 
58
+ ## GitHub Configuration
59
+
60
+ All pull requests are merged by the [Mergify](https://mergify.com) merge queue, configured in `.mergify.yml`. Once a pull request's checks pass, Mergify queues it, brings it up to date with the default branch, waits for the checks again and squash merges it. Draft pull requests and those labelled `do-not-merge` are not merged.
61
+
62
+ The repository must be configured as below so that nothing can be merged without going through the queue.
63
+
64
+ ### Mergify
65
+
66
+ Install the [Mergify GitHub App](https://github.com/apps/mergify) and give it access to this repository.
67
+
68
+ ### Pull request settings
69
+
70
+ In **Settings → General → Pull Requests**:
71
+
72
+ * Allow squash merging only (untick merge commits and rebase merging), matching the queue's merge method.
73
+ * Untick **Allow auto-merge**, because GitHub's own auto-merge merges outside the queue.
74
+ * Tick **Automatically delete head branches**.
75
+
76
+ ### Branch ruleset
77
+
78
+ In **Settings → Rules → Rulesets**, create a branch ruleset with enforcement **Active** that targets the default branch, and set:
79
+
80
+ * **Bypass list**: the **Mergify** app only, in **Exempt** mode. Do not add admins or other roles, as anyone on this list can merge without the queue.
81
+ * **Restrict updates**: only bypass actors can update the branch, so pull requests cannot be merged from the GitHub UI or CLI and commits cannot be pushed directly.
82
+ * **Restrict deletions** and **Block force pushes**.
83
+ * **Require a pull request before merging**, with 0 required approvals.
84
+ * **Require status checks to pass**, listing the checks that `.mergify.yml` waits for: `build`, `package-js`, `package-python`. Leave **Require branches to be up to date before merging** unticked, as the queue already updates and retests each pull request.
85
+
86
+ Do not enable GitHub's own **Require merge queue** rule, as it competes with Mergify.
87
+
88
+ If the queue is unavailable and a change has to be merged, add yourself to the bypass list temporarily and remove yourself afterwards.
89
+
58
90
  ## Creating a New Project
59
91
 
60
92
  ```
@@ -11,4 +11,4 @@ src/projen_modules.egg-info/dependency_links.txt
11
11
  src/projen_modules.egg-info/requires.txt
12
12
  src/projen_modules.egg-info/top_level.txt
13
13
  src/projen_modules/_jsii/__init__.py
14
- src/projen_modules/_jsii/projen-modules@3.0.2.jsii.tgz
14
+ src/projen_modules/_jsii/projen-modules@3.1.0.jsii.tgz
File without changes
File without changes