Skip to content

Commit a2dbb8d

Browse files
jorgenptdanbrakeley
authored andcommitted
Minor autoformatting of README
1 parent faee25d commit a2dbb8d

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,11 @@
1212

1313
`p4harmonize` was built with Unreal Engine source in mind, where the Epic licensee perforce server is used as the source, and a dedicated stream on a project's perforce server is used as the destination. It is intended to be used with a setup similar to [the one recommended by Epic](https://docs.unrealengine.com/4.26/en-US/ProgrammingAndScripting/ProgrammingWithCPP/DownloadingSourceCode/UpdatingSourceCode/#integrating,merging,andbranching). For example, a recent Unreal project I worked on had the following setup:
1414

15-
name | description
16-
--- | ---
17-
`//proj/engine_epic` | exact copy of a specific UE version from Epic's perforce server (p4harmonize targets this stream, no project-specific changes should ever end up here)
18-
`//proj/engine_merge` | dedicated space for a human to merge main with new engine drops; ideally QA will sign off on a build from this branch before the merged engine changes are brought to main
19-
`//proj/main` | our mainline; lots of people work here, so a broken build can be very costly
15+
| name | description |
16+
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
17+
| `//proj/engine_epic` | exact copy of a specific UE version from Epic's perforce server (p4harmonize targets this stream, no project-specific changes should ever end up here) |
18+
| `//proj/engine_merge` | dedicated space for a human to merge main with new engine drops; ideally QA will sign off on a build from this branch before the merged engine changes are brought to main |
19+
| `//proj/main` | our mainline; lots of people work here, so a broken build can be very costly |
2020

2121
![The output of v0.5.0 when there are no changes](images/0.5.0-no-changes.png)
2222

0 commit comments

Comments
 (0)