Merge branch 'main' into extended_app_description

.github/workflows/auto-label-bot.yml

@@ -8,7 +8,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: Pandapip1/jekyll-label-action@28a89dbbef321fceaf3cff17f4d29c7a033c3d56
+      - uses: SudoWeezy/jekyll-label-action@dist
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
           config-path: config/.jekyll-labels.yml

.github/workflows/ci.yaml

@@ -13,7 +13,7 @@ jobs:
   save-pr:
     name: Save PR Number
     runs-on: ubuntu-latest
-    
+
     steps:
       - name: Save PR number
         env:
@@ -34,28 +34,28 @@ jobs:
   htmlproofer:
     name: HTMLProofer
     runs-on: ubuntu-latest
-    
+
     steps:
       - name: Checkout ARC Repository
         uses: actions/checkout@2541b1294d2704b0964813337f33b291d3f8596b
-      
+
       - name: Install OpenSSL
         run: sudo apt-get update && sudo apt-get install -y libcurl4-openssl-dev
-    
+
       - name: Install Ruby
         uses: ruby/setup-ruby@0a29871fe2b0200a17a4497bae54fe5df0d973aa
         with:
           ruby-version: 2.6.0
           bundler-cache: true
-        
+
       - name: Build Website
         run: |
           bundle exec jekyll doctor
           bundle exec jekyll build
-      
+
       - name: HTML Proofer
         run: bundle exec htmlproofer ./_site --check-html --check-opengraph --report-missing-names --log-level=:debug --assume-extension --empty-alt-ignore --timeframe=6w --disable-external
-      
+
       - name: DNS Validator
         run: bundle exec github-pages health-check
 

.github/workflows/dev-portal-content.yml

@@ -0,0 +1,67 @@
+name: Create Dev Portal Content
+
+on:
+  push:
+    branches:
+      - main # Trigger on changes to the main branch
+    paths:
+      - "ARCs/**" # Only run when files in the ARCs directory are changed
+
+jobs:
+  updateDevportal:
+    runs-on: ubuntu-latest
+
+    steps:
+      # Step 1: Checkout the repository
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      # Step 2: Set execute permission for the scripts and create the content directory if needed
+      - name: Make scripts executable
+        run: |
+          chmod +x _devportal/scripts/update-arcs.sh
+          chmod +x _devportal/scripts/update-guideline.sh
+          chmod +x _devportal/scripts/update-index.sh
+          mkdir -p _devportal/content
+
+      # Step 3: Set up Git identity
+      - name: Set up Git user
+        run: |
+          git config --global user.name 'github-actions'
+          git config --global user.email '[email protected]'
+
+      # Step 4: Run update-arcs.sh script
+      - name: Run update-arcs.sh
+        run: _devportal/scripts/update-arcs.sh
+
+      # Step 5: Run update-guideline.sh script
+      - name: Run update-guideline.sh
+        run: _devportal/scripts/update-guideline.sh
+
+      # Step 6: Run update-index.sh script
+      - name: Run update-index.sh
+        run: _devportal/scripts/update-index.sh
+
+      # Step 7: Force changes to be recognized by Git
+      - name: Touch modified files
+        run: |
+          find _devportal/content -type f -exec touch {} \;
+
+      # Step 8: Commit and force push changes to devportal
+      - name: Commit and force push changes to devportal
+        run: |
+          git add -A  # Ensure all changes are staged
+          git add -f _devportal/content/*
+          git commit -m "Auto-update ARC content and headers"
+          BRANCH_NAME="devportal"
+
+          # Check if the branch exists on the remote
+          if git ls-remote --exit-code --heads origin "$BRANCH_NAME"; then
+            echo "Branch $BRANCH_NAME exists on the remote. Force pushing updates."
+            git push origin main:"$BRANCH_NAME" --force  # Corrected force push from main to devportal
+          else
+            echo "Branch $BRANCH_NAME does not exist. Creating it and pushing."
+            git push origin main:"$BRANCH_NAME" --force  # Create the branch and force push
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -1,4 +1,5 @@
 vendor
 
 .bundle
-_site/*
+_site/*
+_devportal/content/*.md

ARC-template.md

@@ -7,6 +7,7 @@ discussions-to: <URL>
 status: Draft
 type: <Standards Track, Meta, or Informational>
 category (*only required for Standards Track): <Interface, or ARC>
+subcategory: <General, Asa, Application, Explorer or Wallet>
 created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
 requires (*optional): <ARC number(s)>
 ---
@@ -15,7 +16,7 @@ This is the suggested template for new ARCs.
 
 Note that an ARC number will be assigned by an editor. When opening a pull request to submit your ARC, please use an abbreviated title in the filename, `arc-draft_title_abbrev.md`.
 
-The title should be 44 characters or less. It should not repeat the ARC number in title, irrespective of the category. 
+The title should be 44 characters or less. It should not repeat the ARC number in title, irrespective of the category.
 
 ## Abstract
 Abstract is a multi-sentence (short paragraph) technical summary. This should be a very terse and human-readable version of the specification section. Someone should be able to read only the abstract to get the gist of what this specification does.