Merge remote-tracking branch 'origin/main' into DOCS-466

.github/workflows/dependabot.yml → .github/dependabot.yml

@@ -4,4 +4,4 @@ updates:
     directory: "/"
     schedule:
       # Check for updates to GitHub Actions every weekday
-      interval: "daily"
+      interval: "daily"

.github/pull_request_template.md

@@ -1,12 +1,6 @@
-{Short description}
-
-{More details, or remove this line}
+{Description of the change}
 
 -- Remove this line and following from the merge commit message --
 
 {JIRA / GitHub issue, or remove this line}
 {Upstream code PR, or remove this line}
-
-Confirm that tests pass and this change is ready for review:
-- [ ] Local `hugo serve`
-- [ ] Local `vale ./content`

.github/workflows/check_header.yml

@@ -11,10 +11,10 @@ jobs:
 
     steps:
     - name: Checkout repository
-      uses: actions/checkout@v2
+      uses: actions/checkout@v4
 
     - name: Set up Python
-      uses: actions/setup-python@v4
+      uses: actions/setup-python@v5
       with:
         python-version: '3.10'
 

.github/workflows/linkcheck.yml

@@ -1,37 +1,54 @@
 name: Lychee check
 on:
-  pull_request:
-    paths:
-      - '**.md'
+  repository_dispatch:
+  workflow_dispatch:
+  schedule:
+    - cron: "1 0 2 * *" # 12:01 on the 1st of each month
 
 jobs:
-  lychee:
+  linkChecker:
     runs-on: ubuntu-latest
+    permissions:
+      issues: write # required for peter-evans/create-issue-from-file
     steps:
+      # check URLs with Lychee
       - uses: actions/checkout@v4
 
       - name: Get changed files
         id: changed-files
         uses: tj-actions/changed-files@v45
         with:
-          files: "**.md"
+          files: "content/**.md"
 
       - name: Link Checker
         id: lychee
-        uses: lycheeverse/lychee-action@v1.10.0
+        uses: lycheeverse/lychee-action@v2
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
-          args: > 
-          --scheme https --scheme http --verbose --no-cache
-          --user-agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64)"
-          --max-concurrency 5 --retry-count 3 --retry-delay 2
-          ${{ steps.changed-files.outputs.all_changed_files }}
+          args: >-
+            --accept 200,429
+            --base content
+            --no-cache
+            --max-cache-age 1d
+            --user-agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64)"
+            --max-concurrency 5
+            --verbose
+            --no-progress
+            --retry-count 1
+            --retry-delay 2
+            --scheme https
+            --scheme http
+            './content/*.md'
+            './content/*.html'
+          fail: false
         env:
+          # to be used in case rate limits are surpassed
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
 
-      - name: Create PR comment with link reults
-        uses: marocchino/sticky-pull-request-comment@v2
+      - name: Create Issue From File
+        if: steps.lychee.outputs.exit_code != 0
+        uses: peter-evans/create-issue-from-file@v5
         with:
-          header: lychee
-          recreate: true
-          path: ./lychee/out.md
+          title: Link Checker Report
+          content-filepath: ./lychee/out.md
+          labels: report, automated issue

content/guides/hosting/data-security/secure-storage-connector.md

@@ -15,6 +15,24 @@ Bring your own bucket (BYOB) allows you to store W&B artifacts and other related
 * You can specify a sub-path when configuring a bucket, to ensure that W&B does not store any files in a folder at the root of the bucket. It can help you better conform to your organzation's bucket governance policy.
 {{% /alert %}}
 
+## Data stored in the central database vs buckets
+
+When using BYOB functionality, certain types of data will be stored in the W&B central database, and other types will be stored in your bucket. 
+
+### Database
+
+- Metadata for users, teams, artifacts, experiments, and projects
+- Reports
+- Experiment logs
+- System metrics
+
+## Buckets
+
+- Experiment files and metrics
+- Artifact files
+- Media files
+- Run files
+
 ## Configuration options
 There are two scopes you can configure your storage bucket to: at the *Instance level* or at a *Team level*.