Renames to Dev Proxy

Author: waldekmastykarz

.github/CODEOWNERS

@@ -1 +1 @@
-* @microsoft/m365-developer-proxy-write
+* @microsoft/dev-proxy-write

.github/ISSUE_TEMPLATE/bug.yml

@@ -38,13 +38,13 @@ body:
     validations:
       required: true
   - type: input
-    id: m365proxyversion
+    id: devproxyversion
     attributes:
-      label: Microsoft 365 Developer Proxy Version
+      label: Dev Proxy Version
       description: |
         Provide the version of the proxy you are using.
         
-        Execute `m365proxy --version` in your terminal to identify your version
+        Execute `devproxy --version` in your terminal to identify your version
     validations:
       required: true 
   - type: dropdown

.github/dependabot.yml

@@ -1,7 +1,7 @@
 version: 2
 updates:
 - package-ecosystem: nuget
-  directory: "/m365-developer-proxy"
+  directory: "/dev-proxy"
   schedule:
     interval: daily
   open-pull-requests-limit: 5

.github/policies/m365-developer-proxy-branch-protection.yml renamed to .github/policies/dev-proxy-branch-protection.yml

@@ -3,8 +3,8 @@
 
 # File initially created using https://github.com/MIchaelMainer/policyservicetoolkit/blob/main/branch_protection_export.ps1.
 
-name: m365-developer-proxy-branch-protection
-description: Branch protection policy for the m365-developer-proxy repository
+name: dev-proxy-branch-protection
+description: Branch protection policy for the dev-proxy repository
 resource: repository
 configuration:
   branchProtectionRules:

.github/workflows/create-release.yml

@@ -15,19 +15,19 @@ jobs:
           - linux-x64
           - osx-x64
     env:
-      release: 'm365-developer-proxy-${{ matrix.architecture }}-${{  github.ref_name }}'
+      release: 'dev-proxy-${{ matrix.architecture }}-${{  github.ref_name }}'
     steps:
       - uses: actions/checkout@v3
       - name: Setup .NET
         uses: actions/setup-dotnet@v3
         with:
           dotnet-version: 7.0.x
       - name: Publish ${{ matrix.architecture }}
-        run: dotnet publish ./m365-developer-proxy/m365-developer-proxy.csproj -c Release -p:PublishSingleFile=true -r ${{ matrix.architecture }} --self-contained -o ./${{ env.release }}
+        run: dotnet publish ./dev-proxy/dev-proxy.csproj -c Release -p:PublishSingleFile=true -r ${{ matrix.architecture }} --self-contained -o ./${{ env.release }}
       - name: Build plugins
-        run: dotnet build ./m365-developer-proxy-plugins/m365-developer-proxy-plugins.csproj -c Release -r ${{ matrix.architecture }} --no-self-contained
+        run: dotnet build ./dev-proxy-plugins/dev-proxy-plugins.csproj -c Release -r ${{ matrix.architecture }} --no-self-contained
       - name: Add plugins to output
-        run: cp ./m365-developer-proxy/bin/Release/net7.0/${{ matrix.architecture }}/plugins ./${{ env.release }} -r
+        run: cp ./dev-proxy/bin/Release/net7.0/${{ matrix.architecture }}/plugins ./${{ env.release }} -r
       - name: Remove unnecessary files
         run: |
           pushd

.github/workflows/dotnet.yml

@@ -23,12 +23,12 @@ jobs:
     - name: Restore workloads
       run: dotnet workload restore
     - name: Restore dependencies
-      run: dotnet restore m365-developer-proxy.sln
+      run: dotnet restore dev-proxy.sln
     - name: Build
-      run: dotnet build m365-developer-proxy.sln --no-restore
+      run: dotnet build dev-proxy.sln --no-restore
     # We really should have tests, putting these steps here for when we have a build process
     # - name: Test
-    #   run: dotnet test m365-developer-proxy.sln --no-build --verbosity normal --collect:"XPlat Code Coverage"
+    #   run: dotnet test dev-proxy.sln --no-build --verbosity normal --collect:"XPlat Code Coverage"
     # - name: Install report generator
     #   run: dotnet tool install --global dotnet-reportgenerator-globaltool
     # - name: Generate coverage report

.vscode/launch.json

@@ -10,9 +10,9 @@
       "request": "launch",
       "preLaunchTask": "build",
       // If you have changed target frameworks, make sure to update the program path.
-      "program": "${workspaceFolder}/m365-developer-proxy/bin/Debug/net7.0/m365proxy.dll",
+      "program": "${workspaceFolder}/dev-proxy/bin/Debug/net7.0/devproxy.dll",
       "args": [],
-      "cwd": "${workspaceFolder}/m365-developer-proxy/bin/Debug/net7.0",
+      "cwd": "${workspaceFolder}/dev-proxy/bin/Debug/net7.0",
       // For more information about the 'console' field, see https://aka.ms/VSCode-CS-LaunchJson-Console
       "console": "integratedTerminal",
       "stopAtEntry": false,

.vscode/tasks.json

@@ -7,7 +7,7 @@
       "type": "process",
       "args": [
         "build",
-        "${workspaceFolder}/m365-developer-proxy.sln",
+        "${workspaceFolder}/dev-proxy.sln",
         "/property:GenerateFullPaths=true",
         "/consoleloggerparameters:NoSummary"
       ],
@@ -19,7 +19,7 @@
       "type": "process",
       "args": [
         "publish",
-        "${workspaceFolder}/m365-developer-proxy.sln",
+        "${workspaceFolder}/dev-proxy.sln",
         "/property:GenerateFullPaths=true",
         "/consoleloggerparameters:NoSummary"
       ],
@@ -33,7 +33,7 @@
         "watch",
         "run",
         "--project",
-        "${workspaceFolder}/m365-developer-proxy.sln"
+        "${workspaceFolder}/dev-proxy.sln"
       ],
       "problemMatcher": "$msCompile"
     }

CONTRIBUTING.md

@@ -1,14 +1,14 @@
-# Contributing to the Microsoft 365 Developer Proxy
+# Contributing to Dev Proxy
 
-The best way to contribute initially is to download and try the Microsoft 365 Developer Proxy and then give us your feedback, both positive and negative, this will help us shape the future direction of this tool. At present we are not accepting community code contributions but will be opening up to accept pull requests in the future.
+The best way to contribute initially is to download and try Dev Proxy and then give us your feedback, both positive and negative, this will help us shape the future direction of this tool. At present we are not accepting community code contributions but will be opening up to accept pull requests in the future.
 
 ## Our foundation
 
-The Microsoft 365 Developer Proxy is built with .NET 6 and uses the [Titanium.Web.Proxy](https://github.com/justcoding121/titanium-web-proxy).
+The Dev Proxy is built with .NET 6 and uses the [Titanium.Web.Proxy](https://github.com/justcoding121/titanium-web-proxy).
 
 ## Reporting issues and suggesting new features
 
-Please use [GitHub Issues](https://github.com/microsoft/m365-developer-proxy/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) for bug reports and feature request.
+Please use [GitHub Issues](https://github.com/microsoft/dev-proxy/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) for bug reports and feature request.
 
 We highly recommend you browse existing issues first.
 

README.md

@@ -1,14 +1,14 @@
 <h1 align="center">
-    <img alt="Microsoft 365 Developer Proxy" src="./samples/img/microsoft.png" height="78" />
-  <br>Microsoft 365 Developer Proxy<br>
+    <img alt="Dev Proxy" src="./samples/img/microsoft.png" height="78" />
+  <br>Dev Proxy<br>
 </h1>
 
 <h4 align="center">
   Build reliable Microsoft 365 apps
 </h4>
 
 <p align="center">
-    <a href="https://github.com/microsoft/m365-developer-proxy/releases/latest">
+    <a href="https://github.com/microsoft/dev-proxy/releases/latest">
         <img alt="Download Now" src="https://img.shields.io/badge/download-now-green?style=for-the-badge">
     </a>
 </p>
@@ -20,7 +20,7 @@
 
 <p align="center">
   <a href="#get-started">Get started</a> |
-  <a href="https://github.com/microsoft/m365-developer-proxy/wiki/">Documentation</a>
+  <a href="https://github.com/microsoft/dev-proxy/wiki/">Documentation</a>
 </p>
 
 <p align="center">
@@ -36,7 +36,7 @@
     <svg aria-hidden="true" height="16" viewBox="0 0 16 16" version="1.1" width="16" data-view-component="true" class="octicon octicon-device-camera-video">
     <path d="M16 3.75v8.5a.75.75 0 0 1-1.136.643L11 10.575v.675A1.75 1.75 0 0 1 9.25 13h-7.5A1.75 1.75 0 0 1 0 11.25v-6.5C0 3.784.784 3 1.75 3h7.5c.966 0 1.75.784 1.75 1.75v.675l3.864-2.318A.75.75 0 0 1 16 3.75Zm-6.5 1a.25.25 0 0 0-.25-.25h-7.5a.25.25 0 0 0-.25.25v6.5c0 .138.112.25.25.25h7.5a.25.25 0 0 0 .25-.25v-6.5ZM11 8.825l3.5 2.1v-5.85l-3.5 2.1Z"></path>
 </svg>
-    <span aria-label="" class="m-1">📽️ Simulate throttling using Microsoft 365 Developer Proxy</span>
+    <span aria-label="" class="m-1">📽️ Simulate throttling using Dev Proxy</span>
     <span class="dropdown-caret"></span>
   </summary>
 
@@ -46,7 +46,7 @@
 </details>
 </p>
 
-Microsoft 365 Developer Proxy is a command line tool for testing Microsoft Graph, SharePoint Online and any other HTTP APIs.
+Dev Proxy is a command line tool for testing Microsoft Graph, SharePoint Online and any other HTTP APIs.
 
 It aims to provide a better way to test applications.
 
@@ -60,14 +60,14 @@ Identify and fix issues in your code before they reach production.
 
 ## Get started
 
-Begin with our [tutorial](https://github.com/microsoft/m365-developer-proxy/wiki/Get-started). It will guide you through the installation process and running the proxy for the first time.
+Begin with our [tutorial](https://github.com/microsoft/dev-proxy/wiki/Get-started). It will guide you through the installation process and running the proxy for the first time.
 
 ## Example
 
 Fail requests (with a 50% chance) and respond with `429 Too Many Requests` or `503 Service Unavailable`:
 
 ```
-m365proxy --failure-rate 50 --no-mocks --allowed-errors 429 503
+devproxy --failure-rate 50 --no-mocks --allowed-errors 429 503
 ```
 
 ## Features
@@ -105,7 +105,7 @@ This project may contain trademarks or logos for projects, products, or services
 
 ## Community Preview
 
-We are working on getting the General Availability (GA) version published within the calendar year 2023. The current state of the Microsoft 365 Developer Proxy enables our team to be transparent and provide more insights on the upcoming features and to provide our worldwide ecosystem an option to directly influence the future of our capabilities. [Your feedback is more than welcome](https://github.com/microsoft/m365-developer-proxy/issues)! You can expect many more new features within the upcoming months before a version that is officially ready for production use and fully supported.
+We are working on getting the General Availability (GA) version published within the calendar year 2023. The current state of Dev Proxy enables our team to be transparent and provide more insights on the upcoming features and to provide our worldwide ecosystem an option to directly influence the future of our capabilities. [Your feedback is more than welcome](https://github.com/microsoft/dev-proxy/issues)! You can expect many more new features within the upcoming months before a version that is officially ready for production use and fully supported.
 
 ## A Microsoft Hackathon 2022 Project