Intial commit for typespec azure libraries

.editorconfig

@@ -0,0 +1,16 @@
+root = true
+
+[*]
+indent_size = 2
+indent_style = space
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+
+[*.cs]
+indent_size = 4
+
+[/packages/samples/**/generated/**]
+generated_code = true
+[/packages/samples/**/output/**]
+generated_code = true

.gitattributes

@@ -0,0 +1,19 @@
+# Don't allow people to merge changes to these generated files, because the result
+# may be invalid. You need to run "rush update" again. Also make GitHub collapse
+# the diff by default for generated files.
+pnpm-lock.yaml                     merge=binary linguist-generated=true
+shrinkwrap.yaml                    merge=binary linguist-generated=true
+npm-shrinkwrap.json                merge=binary linguist-generated=true
+yarn.lock                          merge=binary linguist-generated=true
+common/config/rush/repo-state.json merge=binary linguist-generated=true
+
+# docs/spec.html is also generated and not worth resolving line by line or
+# reviewing or having its diff uncollpased on GitHub. On conflict, pick either
+# side and rebuild to regenerate.
+docs/spec.html               merge=binary linguist-generated=true
+
+# Use unix line endings always, even on Windows
+*                            text=auto eol=lf
+
+# Allow comments in JSON in GitHub rendering
+*.json                       linguist-language=JSON-with-Comments

.github/CODEOWNERS

@@ -0,0 +1,5 @@
+* @bterlson @daviwil @markcowl @allenjzhang @timotheeguerin
+
+/packages/typespec-client-generator-core @lmazuel @m-nash @iscai-msft @srnagar @joheredi
+
+/docs/howtos/DataPlane*/ @lmazuel @m-nash @iscai-msft @srnagar @joheredi

.github/ISSUE_TEMPLATE/0_general.md

@@ -0,0 +1,4 @@
+---
+name: TypeSpec Azure general issue
+about: for general TypeSpec Azure issue.
+---

.github/ISSUE_TEMPLATE/breaking-change-form.md

@@ -0,0 +1,31 @@
+---
+name: Breaking Change Review Form
+about: Requesting Breaking Change Review for TypeSpec Azure features
+title: "[Breaking Change Review] {title} "
+labels: Breaking Change Review
+---
+
+**Describe the breaking change**
+A clear and concise description of what the proposed change is.
+
+**Back-compat design to avoid immediate breaking**
+Any back-compat design:
+
+**Link to detailed breaking design**
+Link:
+
+**Impact**
+This change affecting:
+
+- [ ] ARM
+- [ ] Data-plane
+- [ ] Existing specs: approx. # of service/spec impacted
+- [ ] New specs
+- [ ] Emitters
+- [ ] SDK
+
+**Targeted Sprint**
+Sprint:
+
+**Additional information**
+Add any other information about the change including fixes for here.

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,19 @@
+---
+name: Bug Report
+about: Report bugs or unexpected behaviors of TypeSpec Azure
+title: "[Bug] {Bug title} "
+labels: bug
+assignees: ""
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,18 @@
+---
+name: Feature Request
+about: Request TypeSpec Azure features
+title: "[Feature Request] {Title} "
+assignees: ""
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/onboarding-request.md

@@ -0,0 +1,40 @@
+---
+name: Onboarding request
+about: One time onboarding form to help TypeSpec team to provide better support.
+title: "[Onboarding] {ProviderName} {ARM|Data-plane} "
+labels: onboarding
+assignees: ""
+---
+
+**Please update issue title with provider name and select ARM or Data-plane.**
+
+---
+
+**Service Team Contacts**
+Dev:
+PM:
+
+**Tell us what stage you are currently at with TypeSpec for your API definition**
+
+- [ ] Just heard about TypeSpec, tell me more.
+- [ ] Started modeling with TypeSpec.
+- [ ] Dogfooding with TypeSpec.
+- [ ] Going Private Preview with TypeSpec.
+- [ ] Going for Public Preview with TypeSpec.
+- [ ] We are live.
+
+**What's your next milestone **
+
+1. Milestone: Private Preview | Public Preview
+
+- Target Date:
+
+2. Milestone: Private Preview | Public Preview
+
+- Target Date:
+
+**Link to your repo if available**
+[Repo Link](...)
+
+**Additional notes or questions**
+Add any other context or questions here.

.github/dependabot.yml

@@ -0,0 +1,17 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "gitsubmodule"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Auto update the cadl-ranch-specs version used for e2e tests. It is pinned instead of always using the latest so we don't have a failure showing in random PRs blocking the flow.
+  - package-ecosystem: "npm"
+    directory: "/packages/e2e-tests/cadl-ranch-specs"
+    schedule:
+      interval: "daily"

.github/policies/issues.add-labels.yml

@@ -0,0 +1,47 @@
+id:
+name: New Issue Assign labels
+description: Assign labels to new issues
+owner:
+resource: repository
+disabled: false
+where:
+configuration:
+  resourceManagementConfiguration:
+    scheduledSearches: []
+    eventResponderTasks:
+      - description: Adds `needs-triage` label for new unassigned issues
+        if:
+          - payloadType: Issues
+          - isAction:
+              action: Opened
+          - and:
+              - not:
+                  and:
+                    - isAssignedToSomeone
+        then:
+          - addLabel:
+              label: needs-triage
+
+      - description: Adds `needs-triage` label for new issues reported by non contributors
+        if:
+          - payloadType: Issues
+          - isAction:
+              action: Opened
+          - and:
+              - not:
+                  activitySenderHasPermission:
+                    permission: Write
+              - not:
+                  activitySenderHasAssociation:
+                    association: Member
+              - not:
+                  activitySenderHasAssociation:
+                    association: Collaborator
+              - not:
+                  activitySenderHasPermission:
+                    permission: Admin
+        then:
+          - addLabel:
+              label: customer-reported
+onFailure:
+onSuccess:

.github/workflows/codeql.yml

@@ -0,0 +1,69 @@
+name: "CodeQL"
+
+on:
+  push:
+    branches: ["main", "release/*"]
+  pull_request:
+    branches: ["main", "release/*"]
+  schedule:
+    - cron: "30 3 * * 3"
+
+jobs:
+  analyze:
+    name: Analyze
+    # Runner size impacts CodeQL analysis time. To learn more, please see:
+    #   - https://gh.io/recommended-hardware-resources-for-running-codeql
+    #   - https://gh.io/supported-runners-and-hardware-resources
+    #   - https://gh.io/using-larger-runners
+    # Consider using larger runners for possible analysis time improvements.
+    runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
+    timeout-minutes: ${{ (matrix.language == 'swift' && 120) || 360 }}
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: ["javascript-typescript"]
+        # CodeQL supports [ 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift' ]
+        # Use only 'java-kotlin' to analyze code written in Java, Kotlin or both
+        # Use only 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
+        # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      # Initializes the CodeQL tools for scanning.
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v2
+        with:
+          languages: ${{ matrix.language }}
+          # If you wish to specify custom queries, you can do so here or in a config file.
+          # By default, queries listed here will override any specified in a config file.
+          # Prefix the list here with "+" to use these queries and those in the config file.
+
+          # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
+          # queries: security-extended,security-and-quality
+
+      # Autobuild attempts to build any compiled languages (C/C++, C#, Go, Java, or Swift).
+      # If this step fails, then you should remove it and run the build manually (see below)
+      - name: Autobuild
+        uses: github/codeql-action/autobuild@v2
+
+      # ℹ️ Command-line programs to run using the OS shell.
+      # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
+
+      #   If the Autobuild fails above, remove it and uncomment the following three lines.
+      #   modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance.
+
+      # - run: |
+      #     echo "Run, Build Application using script"
+      #     ./location_of_script_within_repo/buildscript.sh
+
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@v2
+        with:
+          category: "/language:${{matrix.language}}"

.github/workflows/merge-release-in-main.yml

@@ -0,0 +1,48 @@
+name: Merge release branch back into main
+
+on:
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+  push:
+    branches:
+      - "release/*"
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  id-token: write
+  contents: write
+  pull-requests: write
+
+jobs:
+  # Create PR
+  create:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+
+      - name: Generate branch name
+        id: branchname
+        run: |
+          echo "::set-output name=branchname::backmerge/${{ github.ref_name }}-$(date +'%Y-%m-%d')"
+      - name: Create branch
+        run: |
+          branch="${{ steps.branchname.outputs.branchname }}"
+          git checkout -b $branch
+          git push --set-upstream origin $branch --force
+
+      # ---
+      # Unfortunately, this step is no longer possible due to security constraints.
+      # User will have to create the PR manually until we can get a way to create a PR here.
+      # ---
+      #- name: create pull request
+      #  id: open-pr
+      #  uses: repo-sync/pull-request@v2
+      # with:
+      #    github_token: ${{ secrets.GITHUB_TOKEN }}
+      #    source_branch: ${{ steps.branchname.outputs.branchname }}
+      #    destination_branch: ${{ github.event.repository.default_branch }}
+      #    pr_title: "[Automated] Merge ${{ github.ref_name }} into ${{ github.event.repository.default_branch }}"
+      #    pr_body: "Merge ${{github.ref}} back into ${{ github.event.repository.default_branch }}"