paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 43 Packages Projects Releases Wiki Activity

docs: update linking-local-packages.md

Browse Source 
Fix a minor typo

Signed-off-by: Thomas Cardonne <thomas.cardonne@adevinta.com>
This commit is contained in:
Thomas Cardonne
2024-11-28 16:53:53 +01:00
committed by GitHub
parent e61a2e36de
commit c0805d94ef
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tooling/local-dev/linking-local-packages.md
+1 -1
View File
@@ -57,7 +57,7 @@ After making local changes to a package in an external workspace you might often
For example, if you've made changes to the `@backstage/backend-app-api` package in a local clone of the main `backstage` repository, you can generate a patch for your internal project as follows:
```bash title="Run in the cloned backstage repository"
yarn backstage-repo-tools generate patch @backstage/backend-app-api --target ../our-developer-portal
yarn backstage-repo-tools generate-patch @backstage/backend-app-api --target ../our-developer-portal
```
This will generate a patch file in your `our-developer-portal` workspace. The patch will be based on the most recently released version of the source package, with the additional changes on top.