- Using a text editor or CSV-compatible spreadsheet software, open conflicts.csv.
- With guidance from the examples and reference tables below, review the conflicts.csv file to ensure that the proper actions will be taken upon import.
The conflicts.csv file contains a migration map of conflicts and recommended actions. A migration map lists out both what data is being migrated from the source, and how the data will be applied to the target.
Each row in conflicts.csv provides the following information:
|The type of data being changed.|
|The source URL of the data.|
|The expected target URL of the data.|
|The preferred action |
There are several different mapping actions that
ghe-migrator can take when transferring data:
|(default) Data from the source is imported to the target.||All record types|
|Data from the source is replaced by existing data on the target.||Users, organizations, repositories|
|Data from the source is renamed, then copied over to the target.||Users, organizations, repositories|
|If the target exists, map to that target. Otherwise, rename the imported model.||Users|
|Data from the source is combined with existing data on the target.||Teams|
We strongly suggest you review the conflicts.csv file and use
ghe-migrator audit to ensure that the proper actions are being taken. If everything looks good, you can continue to "Applying the imported data on GitHub Enterprise Server".