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: .github/PULL_REQUEST_TEMPLATE.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
This repository uses Markdown files to define changelog entries. If the changes in this pull request are **user-facing**, please create a changelog entry by running the following command:
4
4
5
-
yarn run nice
5
+
pnpm run nice
6
6
7
7
This will generate a `*.md` file in the `.changelog/` directory for your description. You can create as many as you need.
Copy file name to clipboardExpand all lines: README.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,10 +7,11 @@
7
7
8
8
Multi-repo manager for git. A tool for managing projects build using multiple repositories.
9
9
10
-
`mrgit` is designed to work with [yarn workspaces](https://yarnpkg.com/lang/en/docs/workspaces/) and [Lerna](https://github.com/lerna/lerna) out of the box, hence, it mixes the "package" and "repository" concepts. In other words, every repository is meant to be a single [npm](https://npmjs.com) package. It doesn't mean that you must use it with Lerna and npm, but don't be surprised that mrgit talks about "packages" and works best with npm packages.
10
+
`mrgit` is designed to work with [workspaces](https://pnpm.io/workspaces) and [Lerna](https://github.com/lerna/lerna) out of the box, hence, it mixes the "package" and "repository" concepts. In other words, every repository is meant to be a single [npm](https://npmjs.com) package. It doesn't mean that you must use it with Lerna and npm, but don't be surprised that mrgit talks about "packages" and works best with npm packages.
11
11
12
12
# Table of content
13
13
14
+
1.[Cloning](#cloning)
14
15
1.[Installation](#installation)
15
16
1.[Usage](#usage)
16
17
1.[Configuration](#configuration)
@@ -34,6 +35,15 @@ Multi-repo manager for git. A tool for managing projects build using multiple re
34
35
1.[`checkout` or `co`](#checkout-alias-co)
35
36
1.[Projects using mrgit](#projects-using-mrgit)
36
37
38
+
## Cloning
39
+
40
+
> [!NOTE]
41
+
> This project requires **pnpm v10** or higher. You can check your version with `pnpm --version` and update if needed with `npm install -g pnpm@latest`.
42
+
43
+
1. Clone this repository.
44
+
1. Do `pnpm install` inside.
45
+
1. You're ready to go!
46
+
37
47
## Installation
38
48
39
49
```bash
@@ -517,7 +527,7 @@ Before you start, you need to prepare the changelog entries.
517
527
518
528
1. Make sure the `#master` branch is up-to-date: `git fetch && git checkout master && git pull`.
519
529
1. Prepare a release branch: `git checkout -b release-[YYYYMMDD]` where `YYYYMMDD` is the current day.
520
-
1. Generate the changelog entries: `yarn run release:prepare-changelog`.
530
+
1. Generate the changelog entries: `pnpm run release:prepare-changelog`.
521
531
* You can specify the release date by passing the `--date` option, e.g., `--date=2025-06-11`.
522
532
* By passing the `--dry-run` option, you can check what the script will do without actually modifying the files.
523
533
* Read all the entries, correct poor wording and other issues, wrap code names in backticks to format them, etc.
0 commit comments