Main->Master

.git-blame-ignore-revs

@@ -0,0 +1,15 @@
+# List of whitespace-only commits to ignore in the Git blame;
+# to improve tracking changes and avoid noise
+58db4e3419bf1e5cc1bb61fcd7ce2ebbca89243a
+efb3338f5cf0eec21e8a75abc62ee14965cb4a7e
+3859f6ffc088b2ae78748abc84986f4adcadcd41
+d6569192fc91167f555c3eff58402ff01f1197ea
+67de97a492c9389f95499db38f9474a1c20ec585
+a0d085f93eaa69c22449d0217e8daf9eaea2b180
+1cfba25beb46c74bb1debca2bcfe7ac470e96172
+f6bc623284914489e891bbac923feb774c862b99
+abbab3f8b477e917d0a175d0de23cce121096631
+126347025f9cade241beff182738b2527da7535e
+4740b836f300658b27e6ad4d79efac63c9c24c24
+be44bac95670b1cbbc91bd657882d985989846f9
+f67e5704eda60526d495be758572181f01a6cac8

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -20,7 +20,7 @@ body:
       label: Version Information
       description: |
         Please write your Cmder and ConEmu version below.  If applicable, write down your Windows edition too.
-        **👉 See:** [How to find out which Cmder version I'm using](https://github.com/cmderdev/cmder/wiki/Cmder-troubleshooting)
+        **👉 See:** [How to find out which Cmder version I'm using](https://github.com/daxgames/cmder/wiki/Cmder-troubleshooting)
       placeholder: |
         Cmder version:
         Operating system:
@@ -52,13 +52,13 @@ body:
 
           | **README.md** | **Wiki** |
           | ------------- | -------- |
-          | 🌐 [Open Link](https://github.com/cmderdev/cmder/blob/master/README.md) | 🌐 [Open Link](https://github.com/cmderdev/cmder/wiki) |
+          | 🌐 [Open Link](https://github.com/daxgames/cmder/blob/main/README.md) | 🌐 [Open Link](https://github.com/daxgames/cmder/wiki) |
 
           (What you may be asking here could already be explained there!)
 
         - Searched for existing issues (including the **closed** ones) for similar problems here:
 
-          🗃 https://github.com/cmderdev/cmder/issues?q=is:issue
+          🗃 https://github.com/daxgames/cmder/issues?q=is:issue
 
         - Please understand that Cmder uses ConEmu as the default underlying Terminal Emulator.
 
@@ -91,10 +91,10 @@ body:
 
         #### Prerequisites before submitting an issue
         - We do not support any versions older than the current release series, if you are using an older Cmder please update to the latest version first.
-        - Verify that the issue is not already fixed and is reproducible in the **[latest official Cmder version](https://github.com/cmderdev/cmder/releases).**
-        - Check the **[current issues list](https://github.com/cmderdev/cmder/issues?q=is%3Aissue)** and perform a **search of the issue tracker (including closed ones)** to avoid posting a duplicate bug report.
-        - Make sure this is not a support request or question, both of which are better suited for either the **[discussions section](https://github.com/cmderdev/cmder/discussions)**, or the **[questions section](https://github.com/cmderdev/cmder/issues/new?template=question.yml)**.
-        - Verify that the **[wiki](https://github.com/cmderdev/cmder/wiki)** did not contain a suitable solution either.
+        - Verify that the issue is not already fixed and is reproducible in the **[latest official Cmder version](https://github.com/daxgames/cmder/releases).**
+        - Check the **[current issues list](https://github.com/daxgames/cmder/issues?q=is%3Aissue)** and perform a **search of the issue tracker (including closed ones)** to avoid posting a duplicate bug report.
+        - Make sure this is not a support request or question, both of which are better suited for either the **[discussions section](https://github.com/daxgames/cmder/discussions)**, or the **[questions section](https://github.com/daxgames/cmder/issues/new?template=question.yml)**.
+        - Verify that the **[wiki](https://github.com/daxgames/cmder/wiki)** did not contain a suitable solution either.
 
         Thank you for making sure you are opening a new valid issue! ♥
 

.github/ISSUE_TEMPLATE/config.yml

@@ -1,9 +1,9 @@
 blank_issues_enabled: false
 contact_links:
   - name: 📄 Wiki
-    url: "https://github.com/cmderdev/cmder/wiki"
+    url: "https://github.com/daxgames/cmder/wiki"
     about: "Consult the wiki first, it might already contain the information you are looking for"
 
   - name: 💬 Discussions
-    url: "https://github.com/cmderdev/cmder/discussions"
+    url: "https://github.com/daxgames/cmder/discussions"
     about: "Please ask questions related to usage/setup/support/non-issue development discussion in the Discussions section"

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -16,7 +16,7 @@ body:
 
         - Searched for existing issues (including the **closed** ones) for similar feature requests here:
 
-          🗃 https://github.com/cmderdev/cmder/issues?q=is:issue
+          🗃 https://github.com/daxgames/cmder/issues?q=is:issue
 
         - If you are opening the feature request regarding any of the **upstream technologies** that are used by Cmder, please open the feature request at the corresponding upstream repos instead:
             - **[Clink](https://github.com/chrisant996/clink)**, the default shell in Cmder
@@ -28,7 +28,7 @@ body:
 
           You may already have an answer under the Guides or Questions section.
 
-          For a list of labels, visit **[🌐 Labels](https://github.com/cmderdev/cmder/labels)**.
+          For a list of labels, visit **[🌐 Labels](https://github.com/daxgames/cmder/labels)**.
 
           (Be sure to also check “Closed” issues in the labels section!)
 

.github/ISSUE_TEMPLATE/question.yml

@@ -13,15 +13,15 @@ body:
 
           | **README.md** | **Wiki** | **Issues** |
           | ------------- | -------- | ---------- |
-          | 🌐 [Open Link](https://github.com/cmderdev/cmder/blob/master/README.md) | 🌐 [Open Link](https://github.com/cmderdev/cmder/wiki) | 🗃 [Open Link](https://github.com/cmderdev/cmder/issues?q=is:issue) |
+          | 🌐 [Open Link](https://github.com/daxgames/cmder/blob/main/README.md) | 🌐 [Open Link](https://github.com/daxgames/cmder/wiki) | 🗃 [Open Link](https://github.com/daxgames/cmder/issues?q=is:issue) |
 
           (What you may be asking here could already be explained there!)
 
         - If you would like to ask for guides on how to integrate Cmder with your favorite IDE of choice, or how to perform a specific task with Cmder, make sure you visit our label section first.
 
-          You may already have an answer under the [💬 Guides](https://github.com/cmderdev/cmder/issues?q=label%3A%22%F0%9F%92%AC+Type%3A+Guide%22), [📖 Documentation](https://github.com/cmderdev/cmder/issues?q=label%3A%22%F0%9F%93%96+Documentation%22) or [❔ Questions](https://github.com/cmderdev/cmder/issues?q=is%3Aissue+label%3A%22%E2%9D%94+Type%3A+Question%22) section.
+          You may already have an answer under the [💬 Guides](https://github.com/daxgames/cmder/issues?q=label%3A%22%F0%9F%92%AC+Type%3A+Guide%22), [📖 Documentation](https://github.com/daxgames/cmder/issues?q=label%3A%22%F0%9F%93%96+Documentation%22) or [❔ Questions](https://github.com/daxgames/cmder/issues?q=is%3Aissue+label%3A%22%E2%9D%94+Type%3A+Question%22) section.
 
-          For a list of labels, visit **[Labels](https://github.com/cmderdev/cmder/labels)**.
+          For a list of labels, visit **[Labels](https://github.com/daxgames/cmder/labels)**.
 
           (Be sure to also check “Closed” issues in the labels section!)
 

.github/dependabot.yml

@@ -1,7 +1,12 @@
+# 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:
   # Enable version updates for GitHub Actions
-  - package-ecosystem: "github-actions"
+  - package-ecosystem: "github-actions" # See documentation for possible values
     directory: "/" # Location of package manifests
     schedule:
       interval: "weekly"

.github/workflows/branches.yml

@@ -2,7 +2,7 @@ name: Update branches
 
 # Controls when the action will run.
 on:
-  # Triggers the workflow on push events for the development branch
+  # Triggers the workflow on push events for the dev branch
   push:
     branches: [ master ]
 
@@ -11,8 +11,8 @@ on:
 
 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
-  # This job updates the development branch with the master branch
-  update-development:
+  # This job updates the dev branch with the master branch
+  update-dev:
     # The type of runner that the job will run on
     runs-on: ubuntu-latest
 
@@ -33,28 +33,28 @@ jobs:
           echo "| Property | Value |" >> $GITHUB_STEP_SUMMARY
           echo "| --- | --- |" >> $GITHUB_STEP_SUMMARY
           echo "| Source Branch | \`master\` |" >> $GITHUB_STEP_SUMMARY
-          echo "| Target Branch | \`development\` |" >> $GITHUB_STEP_SUMMARY
+          echo "| Target Branch | \`dev\` |" >> $GITHUB_STEP_SUMMARY
           echo "| Triggered by | @${{ github.actor }} |" >> $GITHUB_STEP_SUMMARY
           echo "| Commit | \`${{ github.sha }}\` |" >> $GITHUB_STEP_SUMMARY
           echo "" >> $GITHUB_STEP_SUMMARY
 
       # Runs a single command using the runners shell
-      - name: Merge master into development
+      - name: Merge master into dev
         run: |
           git config user.name "${{ github.actor }}"
           git config user.email "${{ github.actor }}@users.noreply.github.com"
-          git checkout development
+          git checkout dev
           git merge --no-ff master
-          git push origin development
+          git push origin dev
 
       - name: Summary - Merge completed
         if: success()
         shell: bash
         run: |
           echo "### ✅ Merge Successful" >> $GITHUB_STEP_SUMMARY
           echo "" >> $GITHUB_STEP_SUMMARY
-          echo "The \`master\` branch has been successfully merged into \`development\`." >> $GITHUB_STEP_SUMMARY
+          echo "The \`master\` branch has been successfully merged into \`dev\`." >> $GITHUB_STEP_SUMMARY
           echo "" >> $GITHUB_STEP_SUMMARY
           echo "**Merge type:** No fast-forward merge" >> $GITHUB_STEP_SUMMARY
           echo "" >> $GITHUB_STEP_SUMMARY
-          echo "> The development branch is now synchronized with the latest changes from master." >> $GITHUB_STEP_SUMMARY
+          echo "> The dev branch is now synchronized with the latest changes from master." >> $GITHUB_STEP_SUMMARY