@git.zone/cli 1.12.6 → 1.12.8
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.
- package/dist_ts/00_commitinfo_data.js +3 -3
- package/npmextra.json +13 -8
- package/package.json +22 -17
- package/readme.md +69 -105
- package/ts/00_commitinfo_data.ts +2 -2
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
*/
|
|
4
4
|
export const commitinfo = {
|
|
5
5
|
name: '@git.zone/cli',
|
|
6
|
-
version: '1.12.
|
|
7
|
-
description: 'A CLI
|
|
6
|
+
version: '1.12.8',
|
|
7
|
+
description: 'A comprehensive CLI tool for enhancing and managing local development workflows with gitzone utilities, focusing on project setup, version control, code formatting, and template management.'
|
|
8
8
|
};
|
|
9
|
-
//# sourceMappingURL=data:application/json;base64,
|
|
9
|
+
//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiMDBfY29tbWl0aW5mb19kYXRhLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vdHMvMDBfY29tbWl0aW5mb19kYXRhLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiJBQUFBOztHQUVHO0FBQ0gsTUFBTSxDQUFDLE1BQU0sVUFBVSxHQUFHO0lBQ3hCLElBQUksRUFBRSxlQUFlO0lBQ3JCLE9BQU8sRUFBRSxRQUFRO0lBQ2pCLFdBQVcsRUFBRSwrTEFBK0w7Q0FDN00sQ0FBQSJ9
|
package/npmextra.json
CHANGED
|
@@ -10,21 +10,26 @@
|
|
|
10
10
|
"githost": "gitlab.com",
|
|
11
11
|
"gitscope": "gitzone/private",
|
|
12
12
|
"gitrepo": "gitzone",
|
|
13
|
-
"description": "A CLI
|
|
13
|
+
"description": "A comprehensive CLI tool for enhancing and managing local development workflows with gitzone utilities, focusing on project setup, version control, code formatting, and template management.",
|
|
14
14
|
"npmPackagename": "@gitzone_private/gitzone",
|
|
15
15
|
"license": "MIT",
|
|
16
16
|
"keywords": [
|
|
17
17
|
"CLI",
|
|
18
|
-
"development",
|
|
19
|
-
"
|
|
20
|
-
"npm",
|
|
21
|
-
"TypeScript",
|
|
22
|
-
"automation",
|
|
18
|
+
"local development",
|
|
19
|
+
"gitzone utilities",
|
|
23
20
|
"project setup",
|
|
21
|
+
"version control",
|
|
24
22
|
"code formatting",
|
|
23
|
+
"template management",
|
|
24
|
+
"npm packages",
|
|
25
|
+
"TypeScript",
|
|
26
|
+
"automation",
|
|
27
|
+
"commit management",
|
|
25
28
|
"template creation",
|
|
26
|
-
"
|
|
27
|
-
"
|
|
29
|
+
"meta project management",
|
|
30
|
+
"sync",
|
|
31
|
+
"Docker",
|
|
32
|
+
"CI/CD"
|
|
28
33
|
]
|
|
29
34
|
}
|
|
30
35
|
},
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@git.zone/cli",
|
|
3
3
|
"private": false,
|
|
4
|
-
"version": "1.12.
|
|
5
|
-
"description": "A CLI
|
|
4
|
+
"version": "1.12.8",
|
|
5
|
+
"description": "A comprehensive CLI tool for enhancing and managing local development workflows with gitzone utilities, focusing on project setup, version control, code formatting, and template management.",
|
|
6
6
|
"main": "dist_ts/index.ts",
|
|
7
7
|
"typings": "dist_ts/index.d.ts",
|
|
8
8
|
"type": "module",
|
|
@@ -16,16 +16,21 @@
|
|
|
16
16
|
},
|
|
17
17
|
"keywords": [
|
|
18
18
|
"CLI",
|
|
19
|
-
"development",
|
|
20
|
-
"
|
|
21
|
-
"npm",
|
|
22
|
-
"TypeScript",
|
|
23
|
-
"automation",
|
|
19
|
+
"local development",
|
|
20
|
+
"gitzone utilities",
|
|
24
21
|
"project setup",
|
|
22
|
+
"version control",
|
|
25
23
|
"code formatting",
|
|
24
|
+
"template management",
|
|
25
|
+
"npm packages",
|
|
26
|
+
"TypeScript",
|
|
27
|
+
"automation",
|
|
28
|
+
"commit management",
|
|
26
29
|
"template creation",
|
|
27
|
-
"
|
|
28
|
-
"
|
|
30
|
+
"meta project management",
|
|
31
|
+
"sync",
|
|
32
|
+
"Docker",
|
|
33
|
+
"CI/CD"
|
|
29
34
|
],
|
|
30
35
|
"author": "Task Venture Capital GmbH",
|
|
31
36
|
"license": "MIT",
|
|
@@ -34,13 +39,13 @@
|
|
|
34
39
|
},
|
|
35
40
|
"homepage": "https://gitlab.com/gitzone/private/gitzone#readme",
|
|
36
41
|
"devDependencies": {
|
|
37
|
-
"@git.zone/tsbuild": "^2.2.
|
|
42
|
+
"@git.zone/tsbuild": "^2.2.1",
|
|
38
43
|
"@git.zone/tsrun": "^1.3.3",
|
|
39
|
-
"@git.zone/tstest": "^1.0.
|
|
40
|
-
"@types/node": "^22.
|
|
44
|
+
"@git.zone/tstest": "^1.0.96",
|
|
45
|
+
"@types/node": "^22.13.5"
|
|
41
46
|
},
|
|
42
47
|
"dependencies": {
|
|
43
|
-
"@git.zone/tsdoc": "^1.4.
|
|
48
|
+
"@git.zone/tsdoc": "^1.4.4",
|
|
44
49
|
"@git.zone/tspublish": "^1.9.1",
|
|
45
50
|
"@push.rocks/commitinfo": "^1.0.12",
|
|
46
51
|
"@push.rocks/early": "^4.0.4",
|
|
@@ -51,7 +56,7 @@
|
|
|
51
56
|
"@push.rocks/smartchok": "^1.0.34",
|
|
52
57
|
"@push.rocks/smartcli": "^4.0.11",
|
|
53
58
|
"@push.rocks/smartdelay": "^3.0.5",
|
|
54
|
-
"@push.rocks/smartfile": "^11.
|
|
59
|
+
"@push.rocks/smartfile": "^11.2.0",
|
|
55
60
|
"@push.rocks/smartgulp": "^3.0.4",
|
|
56
61
|
"@push.rocks/smartinteract": "^2.0.15",
|
|
57
62
|
"@push.rocks/smartjson": "^5.0.20",
|
|
@@ -63,14 +68,14 @@
|
|
|
63
68
|
"@push.rocks/smartobject": "^1.0.12",
|
|
64
69
|
"@push.rocks/smartopen": "^2.0.0",
|
|
65
70
|
"@push.rocks/smartpath": "^5.0.18",
|
|
66
|
-
"@push.rocks/smartpromise": "^4.
|
|
71
|
+
"@push.rocks/smartpromise": "^4.2.3",
|
|
67
72
|
"@push.rocks/smartscaf": "^4.0.15",
|
|
68
|
-
"@push.rocks/smartshell": "^3.2.
|
|
73
|
+
"@push.rocks/smartshell": "^3.2.3",
|
|
69
74
|
"@push.rocks/smartstream": "^3.2.5",
|
|
70
75
|
"@push.rocks/smartunique": "^3.0.9",
|
|
71
76
|
"@push.rocks/smartupdate": "^2.0.6",
|
|
72
77
|
"@types/through2": "^2.0.41",
|
|
73
|
-
"prettier": "^3.
|
|
78
|
+
"prettier": "^3.5.2",
|
|
74
79
|
"through2": "^4.0.2"
|
|
75
80
|
},
|
|
76
81
|
"files": [
|
package/readme.md
CHANGED
|
@@ -1,191 +1,155 @@
|
|
|
1
1
|
# @git.zone/cli
|
|
2
2
|
|
|
3
|
-
A CLI toolbelt to streamline local development cycles by
|
|
3
|
+
A CLI toolbelt to streamline local development cycles by utilizing various gitzone utilities.
|
|
4
4
|
|
|
5
5
|
## Install
|
|
6
6
|
|
|
7
|
-
To
|
|
7
|
+
To begin using `@git.zone/cli`, ensure that Node.js and npm are installed on your system. Once they are set up, install the CLI tool globally with the following command:
|
|
8
8
|
|
|
9
9
|
```shell
|
|
10
10
|
npm install -g @git.zone/cli
|
|
11
11
|
```
|
|
12
12
|
|
|
13
|
-
This
|
|
13
|
+
This command makes `gitzone` or `gzone` accessible from any directory on your system.
|
|
14
14
|
|
|
15
15
|
## Usage
|
|
16
16
|
|
|
17
|
-
The `gitzone` CLI
|
|
17
|
+
The `gitzone` CLI provides a comprehensive set of utilities to optimize and manage the development lifecycle of projects, ranging from project initialization to version control, code formatting, and deployment processes. This usage guide will walk you through the available commands, their use cases, and provide detailed examples.
|
|
18
18
|
|
|
19
|
-
###
|
|
19
|
+
### Initializing a New Project
|
|
20
20
|
|
|
21
|
-
To
|
|
22
|
-
|
|
23
|
-
#### Initialize a New Project
|
|
24
|
-
|
|
25
|
-
`gitzone` can create several types of projects, including standard npm modules, websites using LitElement, and custom web components. To create a new project, you can use the following command:
|
|
21
|
+
To bootstrap a new project aligned with modern TypeScript practices, use gitzone's template command. Choose from a range of templates tailored for different project types:
|
|
26
22
|
|
|
27
23
|
```shell
|
|
28
24
|
gitzone template [templatename]
|
|
29
25
|
```
|
|
30
26
|
|
|
31
|
-
Replace `[templatename]` with
|
|
32
|
-
- `npm`:
|
|
33
|
-
- `website`:
|
|
34
|
-
- `element`:
|
|
27
|
+
Replace `[templatename]` with any of the following:
|
|
28
|
+
- `npm`: Starts an npm module with TypeScript, complete with test and CI/CD integration.
|
|
29
|
+
- `website`: Initializes a LitElement-based frontend application with features such as e2e testing and service worker setup.
|
|
30
|
+
- `element`: Prepares a new standard setup for creating reusable web components with LitElement.
|
|
35
31
|
|
|
36
|
-
Example
|
|
37
|
-
1.
|
|
38
|
-
2. Execute
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
3.
|
|
32
|
+
**Example: Starting a New npm Project**
|
|
33
|
+
1. Navigate to your desired directory in the terminal.
|
|
34
|
+
2. Execute:
|
|
35
|
+
```shell
|
|
36
|
+
gitzone template npm
|
|
37
|
+
```
|
|
38
|
+
3. Respond to the prompts to customize the project settings. This includes setting up essential metadata such as name and repository information.
|
|
43
39
|
|
|
44
|
-
|
|
40
|
+
### Committing Changes
|
|
45
41
|
|
|
46
|
-
|
|
42
|
+
Standardizing commit messages and versionning with gitzone:
|
|
47
43
|
|
|
48
44
|
```shell
|
|
49
45
|
gitzone commit
|
|
50
46
|
```
|
|
51
47
|
|
|
52
|
-
This command
|
|
48
|
+
This command provides an interactive prompt to create a conventional commit message, which will be automatically versioned based on the significance of the changes like `fix`, `feat`, or `BREAKING CHANGE`.
|
|
53
49
|
|
|
54
|
-
|
|
50
|
+
### Handling Package Deprecation
|
|
55
51
|
|
|
56
|
-
|
|
52
|
+
Replace an outdated package with a new one for your team and users:
|
|
57
53
|
|
|
58
54
|
```shell
|
|
59
55
|
gitzone deprecate
|
|
60
56
|
```
|
|
61
57
|
|
|
62
|
-
|
|
58
|
+
The utility collects information about old and new package names through interactive prompts, and proceeds with deprecation notices in npm, guiding users towards the updated package.
|
|
63
59
|
|
|
64
|
-
|
|
60
|
+
### CI/CD Utilities
|
|
65
61
|
|
|
66
|
-
|
|
62
|
+
Access your project’s CI/CD settings instantly:
|
|
67
63
|
|
|
68
64
|
```shell
|
|
69
65
|
gitzone open ci
|
|
70
66
|
```
|
|
71
67
|
|
|
72
|
-
|
|
68
|
+
This command opens the settings page of the repository’s CI/CD configuration directly from your CLI, thus swiftly transitioning from local tasks to cloud configurations.
|
|
73
69
|
|
|
74
|
-
|
|
70
|
+
### Maintaining Project Cleanliness
|
|
75
71
|
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
1. Navigate to your desired directory.
|
|
79
|
-
2. Run the following command:
|
|
80
|
-
```shell
|
|
81
|
-
gitzone template element
|
|
82
|
-
```
|
|
83
|
-
3. Follow the prompts to set up your web component project.
|
|
84
|
-
|
|
85
|
-
#### Managing Project Lifecycle
|
|
86
|
-
|
|
87
|
-
Commands to manage your project's lifecycle:
|
|
88
|
-
|
|
89
|
-
- **Commit Changes:**
|
|
90
|
-
```shell
|
|
91
|
-
gitzone commit
|
|
92
|
-
```
|
|
93
|
-
- **Deprecate a Package:**
|
|
94
|
-
```shell
|
|
95
|
-
gitzone deprecate
|
|
96
|
-
```
|
|
97
|
-
- **Format Project Files:**
|
|
98
|
-
```shell
|
|
99
|
-
gitzone format
|
|
100
|
-
```
|
|
101
|
-
- **Regenerate Readme:**
|
|
102
|
-
```shell
|
|
103
|
-
gitzone readme
|
|
104
|
-
```
|
|
105
|
-
- **Update Local Repositories:**
|
|
106
|
-
```shell
|
|
107
|
-
gitzone update
|
|
108
|
-
```
|
|
109
|
-
|
|
110
|
-
#### Advanced Scenarios
|
|
111
|
-
|
|
112
|
-
##### Formatting
|
|
113
|
-
|
|
114
|
-
To ensure consistent formatting using Prettier:
|
|
72
|
+
For consistent code formatting across your project:
|
|
115
73
|
|
|
116
74
|
```shell
|
|
117
75
|
gitzone format
|
|
118
76
|
```
|
|
119
77
|
|
|
120
|
-
|
|
78
|
+
This command applies uniform formatting styles using Prettier, ensuring your JS/TS and markdown files align with the project's style guide.
|
|
121
79
|
|
|
122
|
-
|
|
80
|
+
### Lifecycle Management Commands
|
|
81
|
+
|
|
82
|
+
#### Clean Builds
|
|
83
|
+
|
|
84
|
+
Remove generated files and prepare for a fresh build:
|
|
123
85
|
|
|
124
86
|
```shell
|
|
125
|
-
|
|
87
|
+
gitzone clean
|
|
126
88
|
```
|
|
127
89
|
|
|
128
|
-
|
|
90
|
+
This utility cleans up build artifacts from your project directory so that you can run a fresh build without residual clutter affecting outcomes.
|
|
129
91
|
|
|
130
|
-
|
|
92
|
+
#### Sync and meta Configuration
|
|
93
|
+
|
|
94
|
+
To manage metadata that guides your project configurations and module syncing:
|
|
131
95
|
|
|
132
96
|
```shell
|
|
133
|
-
gitzone
|
|
97
|
+
gitzone meta init
|
|
134
98
|
```
|
|
135
99
|
|
|
136
|
-
|
|
100
|
+
This initialization sets the groundwork for supporting gitzone projects by helping you create a `.meta.json` file that tracks subprojects.
|
|
137
101
|
|
|
138
|
-
|
|
139
|
-
gitzone update
|
|
140
|
-
```
|
|
102
|
+
### Advanced Operations
|
|
141
103
|
|
|
142
|
-
|
|
104
|
+
#### Cloud and Docker Integrations
|
|
143
105
|
|
|
144
|
-
|
|
106
|
+
For projects integrating cloud deployment or containerization:
|
|
145
107
|
|
|
146
108
|
```shell
|
|
147
|
-
gitzone
|
|
109
|
+
gitzone docker prune
|
|
148
110
|
```
|
|
149
111
|
|
|
150
|
-
|
|
112
|
+
This utility manages Docker resources by cleaning stale volumes, containers, and images, ensuring efficient resource use.
|
|
151
113
|
|
|
152
|
-
|
|
114
|
+
### Detailed Use Cases
|
|
153
115
|
|
|
154
|
-
|
|
116
|
+
#### **Project Setup and Template Management**
|
|
155
117
|
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
118
|
+
Whether creating an npm module or a web component, the command `gitzone template [templatename]` invokes smart scaffolding processes that automatically set up a robust project environment equipped with modern tooling like TypeScript, Prettier configurations, and testing frameworks.
|
|
119
|
+
|
|
120
|
+
#### **Commit Management**
|
|
121
|
+
|
|
122
|
+
The `gitzone commit` command assures that your commit messages complement semantic versioning practices. It proposes version bumps based on detected changes and helps maintain an accurate project change log.
|
|
159
123
|
|
|
160
|
-
|
|
124
|
+
- **Interactive Commit:** Users engage in dialogues to define commit type (`fix`, `feat`, `BREAKING CHANGE`), scope, and description, resulting in uniform and meaningful commit logs.
|
|
125
|
+
- **Automatic Versioning:** After message crafting, the versioning is attended by bumps similar to npm’s `npm version` with stages such as `major`, `minor`, and `patch`.
|
|
161
126
|
|
|
162
|
-
|
|
127
|
+
#### **Formatting and Configurations**
|
|
163
128
|
|
|
129
|
+
A consistent format yields a professional and readable codebase:
|
|
164
130
|
```shell
|
|
165
|
-
|
|
131
|
+
gitzone format
|
|
166
132
|
```
|
|
167
133
|
|
|
168
|
-
|
|
134
|
+
- **Prettier Integration:** Formats not only TypeScript and JavaScript files but also documents such as `readme.md`, maintaining consistency in both code and documentation style.
|
|
169
135
|
|
|
170
|
-
####
|
|
136
|
+
#### **Synced Meta Projects**
|
|
171
137
|
|
|
172
|
-
|
|
138
|
+
Effectively supervise interconnected repositories or module collections:
|
|
139
|
+
- **Meta Initialization (`meta init`)**: Lay down a foundation for a meta repository that orchestrates multiple projects by overseeing them through a centralized metadata file.
|
|
140
|
+
- **Subproject Operations:** Commands such as `meta update`, `meta add`, `meta remove` enable dynamic management of subprojects, ensuring they remain updated with current features and aligned to the meta repository's standards.
|
|
173
141
|
|
|
174
|
-
|
|
175
|
-
gitzone --loglevel=debug
|
|
176
|
-
```
|
|
142
|
+
#### **CI/CD Integration**
|
|
177
143
|
|
|
178
|
-
|
|
144
|
+
Directly linking your local development processes to continuous integration settings with `gitzone open ci` provides seamless switches between code and configuration in cloud-based environments.
|
|
179
145
|
|
|
180
|
-
|
|
146
|
+
#### **Real-time Docker Management**
|
|
181
147
|
|
|
182
|
-
|
|
183
|
-
gitzone clean
|
|
184
|
-
```
|
|
148
|
+
For developers employing Docker for service deployments, `gitzone docker prune` offers a quick remedy to residual services, optimizing local/docker-storage for a more streamlined experience in container management.
|
|
185
149
|
|
|
186
|
-
###
|
|
150
|
+
### Leveraging gitzone
|
|
187
151
|
|
|
188
|
-
|
|
152
|
+
By mastering the `gitzone` CLI commands, you gain unparalleled efficiency in managing your projects from conception to deployment. Encompassing a wide gamut of functionalities, from initial project scaffolding to synchronization of modularized repositories and beyond, `gitzone` serves as a linchpin for developers intent on optimizing their workflow. Understanding and utilizing its full potential catalyzes development cycles, granting the freedom to focus on innovation, collaboration, and delivering outstanding software products.
|
|
189
153
|
|
|
190
154
|
## License and Legal Information
|
|
191
155
|
|
package/ts/00_commitinfo_data.ts
CHANGED
|
@@ -3,6 +3,6 @@
|
|
|
3
3
|
*/
|
|
4
4
|
export const commitinfo = {
|
|
5
5
|
name: '@git.zone/cli',
|
|
6
|
-
version: '1.12.
|
|
7
|
-
description: 'A CLI
|
|
6
|
+
version: '1.12.8',
|
|
7
|
+
description: 'A comprehensive CLI tool for enhancing and managing local development workflows with gitzone utilities, focusing on project setup, version control, code formatting, and template management.'
|
|
8
8
|
}
|