Folder names prefixed with "."

[greyghostbrewery]

Describe the bug Folder names in this repo are prefixed with a period (".").

This is generally used for hidden folders, and as such causes issues in applications such as File Explorer when "Show Hidden Files and Folders" is disabled.

Is there a reason why the folder names are prefixed with a period as this seems to go against a generally accepted standard for naming conventions?

FYI - this is in reference to the DevOps Pipelines wiki page here: https://github.com/azure/azops/wiki/azure-pipelines

[daltondhcp]

Thanks for reaching out with your question about the .github, .vscode, and .devcontainer directories. It's great to see your engagement with the project!

To clarify, these folders are standard in many GitHub repositories and serve specific purposes:

• .github: This folder typically contains GitHub-specific files like workflow templates for GitHub Actions, issue templates, and contribution guidelines. It helps in automating and streamlining various GitHub processes. For more details, you can check out GitHub's documentation here.

• .vscode: This directory is used when the project is opened in Visual Studio Code (VSCode). It contains settings specific to the editor, such as code formatting rules, recommended extensions, and debug configurations. It ensures a consistent development environment for all contributors. More info can be found on the VSCode documentation page here.

• .devcontainer: This folder holds configuration files for the Visual Studio Code Remote - Containers extension. It allows developers to work in a Docker container environment, ensuring that everyone has the same tools and dependencies, regardless of their local setup. You can learn more about it here.

• .pipelines: This directory typically contains definitions for CI/CD (Continuous Integration/Continuous Deployment) pipelines. It's used to define automated workflows for building, testing, and deploying your code.

These folders are not directly related to the core functionality of the project but are crucial for maintaining consistency and efficiency in development practices, especially in collaborative settings. If they are not relevant to your use case, you can typically ignore them without impacting the main functionality of the project.

Hope this helps! Let us know if you have any more questions.

[greyghostbrewery]

This is actually related to the wiki page listed in the issue, and not the folder names you have listed, specifically the .pipelines & .scripts folders.