[Question] 'Add Existing App' - Keep source folder structure?

[fvet]

Having to move quite some repo's from Azure DevOps to Github repo's (single project repo's), we're considering to use the 'Add Existing App' on a fresh github repo created based on the AL-Go Template.

However, the folder names seem to be regenerated by the github 'Add Existing App' action instead of using the origin / source folder names. All our repo's have the \App and \Test folder structure, containing the main app and a test app. So if no conflicts would arise between the apps discovered, would it be possible to use the original folder names instead?

Azure Devops as-is

• App (with app.json : Companyweb Business Information)
• Test (with app.json : Dynavision CompanyWeb-Test)

Github result

• Companyweb Business Information
• Dynavision CompanyWeb-Test

Expected Github result

• App (with app.json : Companyweb Business Information)
• Test (with app.json : Dynavision CompanyWeb-Test)

[jonaswre]

Hi, a little while ago I've created a repo that helps migrating from the old (Azure DevOps) Hello World to the new GitHub structure.

https://github.com/byndit/AL-Go-Import This even keeps the git history intakt.

Feel free to fork and do what you need with it.

In your Szenario I would probably just script the Prozess using Powershell on my local Maschine.

1. Get all repo urls using the AZ cli.
2. Clone them to your Maschine.
3. Modify the files you need. 3.1 Remove DevOps pipelines 3.2 Add .AL-GO folder 3.3 Add .GitHub Folder 3.4 Add workspace file.
4. Create GitHub Repos using GitHub API
5. Add the GitHub repo as a remote to your local repo
6. Add changes
7. Commit changes
8. Push changes