updating stale

.github/workflows/stale-branches.yml

@@ -0,0 +1,31 @@
+name: Stale Branches
+
+on:
+  schedule:
+    - cron: '30 1 * * *'
+  workflow_dispatch:
+
+permissions:
+  issues: write
+  contents: write
+
+jobs:
+  stale_branches:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Stale Branches
+      uses: crs-k/[email protected]
+      with:
+        repo-token: '${{ secrets.GITHUB_TOKEN }}'
+        days-before-stale: 45
+        days-before-delete: 60
+        comment-updates: false
+        tag-committer: false
+        stale-branch-label: 'stale branch 🗑️'
+        compare-branches: 'info'
+        branches-filter-regex: '^((?!dependabot))'
+        rate-limit: false
+        pr-check: false
+        dry-run: false
+        ignore-issue-interaction: false
+

.github/workflows/stale-issues-pr.yml

@@ -0,0 +1,20 @@
+name: 'Stale Issues and PRs'
+on:
+  schedule:
+    - cron: '30 1 * * *'
+  workflow_dispatch:
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v9
+        with:
+          stale-issue-message: 'This issue is stale because it has been open 21 days with no activity. Remove stale label or comment or this will be closed in 5 days.'
+          stale-pr-message: 'This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.'
+          close-issue-message: 'This issue was closed because it has been stalled for 5 days with no activity.'
+          close-pr-message: 'This PR was closed because it has been stalled for 7 days with no activity.'
+          days-before-issue-stale: 21
+          days-before-pr-stale: 30
+          days-before-issue-close: 5
+          days-before-pr-close: 7

README.md

@@ -1,3 +1,5 @@
+[![Stale Issues and PRs](https://github.com/Azure/arc_jumpstart_docs/actions/workflows/stale-issues-pr.yml/badge.svg?branch=main)](https://github.com/Azure/arc_jumpstart_docs/actions/workflows/stale-issues-pr.yml) [![Stale Branches](https://github.com/Azure/arc_jumpstart_docs/actions/workflows/stale-branches.yml/badge.svg)](https://github.com/Azure/arc_jumpstart_docs/actions/workflows/stale-branches.yml)
+
 # Arc Jumpstart documentation
 
 Welcome to the Arc Jumpstart documentation repository! This repository is your go-to resource for in-depth guides, best practices, and detailed documentation related to Azure Arc. Whether you're a beginner exploring the basics or an experienced user optimizing your deployment, you'll find valuable insights tailored to your needs. This repository complements our [source code repository](https://aka.ms/JumpstartGitHubCode) and acts has the documentation source repository which populates the [Arc Jumpstart](https://aka.ms/arcjumpstart) website.

docs/FAQ/_index.md

@@ -9,7 +9,7 @@ weight: 8
 
 ## Can I contribute to the Arc Jumpstart?
 
-Absolutely! Arc Jumpstart is a community-driven open source project, and contributions are welcomed. To get started, review the [Jumpstart contribution guidelines](../contribution_guidelines/) and our [Code of Conduct](https://aka.ms/JumpstartCOC).
+Absolutely! Arc Jumpstart is a community-driven open-source project, and contributions are welcomed. To get started, review the [Jumpstart contribution guidelines](../contribution_guidelines/) and our [Code of Conduct](https://aka.ms/JumpstartCOC).
 
 ## Are any of the Arc Jumpstart documents created with AI assistance?
 
@@ -29,7 +29,7 @@ Each Arc Jumpstart scenario and solution describes what is needed to run the aut
 
 ## Is Arc Jumpstart considered "production-ready"?
 
-The intention of the Arc Jumpstart is to focus on the core Azure Arc, edge, and IoT capabilities, deployment scenarios, use cases, and ease of use. It does not focus on Azure best practices, and/or other products or open source projects being leveraged in our code. Jumpstart Scenarios, ArcBox, HCIBox, and Agora are all intended for evaluation, training, and demo purposes only and are not supported for production use cases.
+The intention of the Arc Jumpstart is to focus on the core Azure Arc, edge, and IoT capabilities, deployment scenarios, use cases, and ease of use. It does not focus on Azure best practices, and/or other products or open-source projects being leveraged in our code. Jumpstart Scenarios, ArcBox, HCIBox, and Agora are all intended for evaluation, training, and demo purposes only and are not supported for production use cases.
 
 ## Is there guidance on how to run a demo using the Arc Jumpstart?
 

docs/azure_arc_jumpstart/FAQ/_index.md

@@ -9,4 +9,4 @@ weight: 8
 
 ## Can I contribute to the Arc Jumpstart Scenarios?
 
-Absolutely! Arc Jumpstart Scenarios follows the Arc Jumpstart community-driven open source project vision, and contributions are welcomed. To get started, review the [Jumpstart contribution guidelines](../contribution_guidelines/) and our [Code of Conduct](https://aka.ms/JumpstartCOC).
+Absolutely! Arc Jumpstart Scenarios follows the Arc Jumpstart community-driven open-source project vision, and contributions are welcomed. To get started, review the [Jumpstart contribution guidelines](../contribution_guidelines/) and our [Code of Conduct](https://aka.ms/JumpstartCOC).

docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/gitops/_index.md

@@ -17,9 +17,9 @@ The following Jumpstart scenario will guide you how to use GitOps [GitOps for Az
 - [Deploy EKS cluster and connect it to Azure Arc using Terraform](/azure_arc_jumpstart/azure_arc_k8s/eks/eks_terraform/)
 - [Deploy GKE cluster and connect it to Azure Arc using Terraform](/azure_arc_jumpstart/azure_arc_k8s/gke/gke_terraform/)
 
-  > **Note:** This guide assumes you already have deployed Calico network policy in your cluster. If you haven't, you can use our installation guides for Calico open source or Calico Cloud.
+  > **Note:** This guide assumes you already have deployed Calico network policy in your cluster. If you haven't, you can use our installation guides for Calico open-source or Calico Cloud.
 
-- [Deploy Calico open source in your managed public cluster](https://projectcalico.docs.tigera.io/getting-started/kubernetes/managed-public-cloud/)
+- [Deploy Calico open-source in your managed public cluster](https://projectcalico.docs.tigera.io/getting-started/kubernetes/managed-public-cloud/)
 - [Sign up for a Calico Cloud trial](https://www.calicocloud.io/?utm_campaign=calicocloud&utm_medium=digital&utm_source=microsoft)
 
 Calico Network Policy provides the [Network Set](https://projectcalico.docs.tigera.io/archive/v3.21/reference/resources/networkset) resource to label an arbitrary set of IP subnetworks/CIDRs, allowing it to be matched by Calico policy.