What is the recommended *.gitignore configuration for standard logic app projects (with/without custom code)

[asos-martinsmith]

Currently we are gitignoring the following files (amongst others)

• The *.code-workspace file
• The local.settings.json file
• The .vscode folder (in both the logic app and local function app project if applicable)

This means that if we clone the repo we are not in a position that we can just run the workflow and need to first manually recreate all these files.

What is the recommended practice here? Should we be gitignoring all these files? If so is there any way we can use the extension to recreate these files where missing?

[mark-abrams]

That's a good question and one that I've thought about a few times. I do not exclude the .vscode files, there is nothing sensitive in the files and if you do not include these in a git repo, other developers cannot develop the workflows or run them locally within VS Code without additional actions, and this gets annoying.

[TWolversonReply]

*.code-workspace is a pain to have ignored, as you do on occasion want to add new folders to it. There is known behaviour, that seems like a bug, that paths local to the user's machine are written into the workspace file which seems obviously wrong and something I'd understand you wanting to exclude from source control by ignoring.

I also couldn't get a straight answer on what should and should not be checked in from .vscode - the best I could come up with were that tasks, settings, launch and extensions should be as they are standard, and everything else should be ignored, but there are different statements in different places and most are just someone's opinion.