Tribes GitHub Action

[tomsmith8]

Trigger /sync on Master Updates

• Configure the GitHub Action to watch for updates on both frontend and backend master branches.
• On update, call the Swarm /sync endpoint with a pat params and
  GET https://boltwll.swarm38.sphinx.chat/api/git/sync?source_link=https://github.com/stakwork/sphinx-tribes,https://github.com/stakwork/sphinx-tribes-frontend
• Include pat parameter in the request

name: Stakgraph - Sync Codebase
on:
  push:
    branches:
      - master
jobs:
  sync:
    runs-on: ubuntu-latest
    steps:
      - name: Call Swarm Sync Endpoint
        run: |
          curl -G "https://boltwall.swarm38.sphinx.chat/api/git/sync" \
            --header "x-api-token: ${{ secrets.SWARM_API_KEY }}" \
            --data-urlencode "source_link=https://github.com/stakwork/sphinx-tribes,https://github.com/stakwork/sphinx-tribes-frontend" \
            --data-urlencode "pat=${{ secrets.TRIBES_GITHUB_PAT }}"

@stakwork

[Evanfeenstra]

🤖 Processing your request... (Stakwork run: https://jobs.stakwork.com/admin/projects/114974050)

I've received your message and started working on it. You'll receive a detailed response shortly.

[Evanfeenstra]

Summary

Stakgraph will add a GitHub Action to both sphinx-tribes and sphinx-tribes-frontend repositories to automatically trigger the Swarm /sync endpoint whenever the master branch is updated. This ensures that Swarm stays in sync with the latest codebase changes across both repos.

---

Planned Changes

• Add a GitHub Actions workflow that:
  • Triggers on push events to the master branch.
  • Calls the Swarm /sync endpoint via a GET request.
  • Passes both repository URLs as the source_link parameter.
  • Includes a pat parameter for authentication.
  • Uses the x-api-token header for secure API access.
• Store sensitive values (SWARM_API_KEY, TRIBES_GITHUB_PAT) as GitHub secrets.

---

Files/Areas Affected

• .github/workflows/ (new or updated workflow YAML file)
• GitHub repository settings (to ensure required secrets are present)

---

Next Steps:
Implement and test the workflow in both repositories to confirm Swarm sync is triggered as expected on master updates.

[Evanfeenstra]

Summary

This PR introduces a new GitHub Action workflow that automatically triggers the Swarm /sync endpoint whenever there are updates (pushes) to the master branch. The workflow ensures that both the backend and frontend repositories are synchronized with Swarm, using secure credentials.

---

Changes Made

• New Workflow Added:
  • File: .github/workflows/sync-codebase.yml
  • Trigger: On every push to the master branch.
  • Job:
    • Runs on ubuntu-latest.
    • Executes a curl command to call the Swarm /sync endpoint:
      • Endpoint: https://boltwall.swarm38.sphinx.chat/api/git/sync
      • Parameters:
        • source_link: Includes both backend and frontend repo URLs.
        • pat: Passed securely from GitHub secrets.
      • Header: x-api-token set from GitHub secret.

---

Architecture Improvements

• Automated Synchronization:
  Ensures that any update to the master branch is immediately reflected in Swarm, reducing manual sync steps and potential inconsistencies.

• Secure Credential Management:
  Uses GitHub Actions secrets (SWARM_API_KEY and TRIBES_GITHUB_PAT) to securely handle sensitive tokens.

• Centralized Sync Logic:
  Both backend and frontend repositories are synchronized in a single action, simplifying maintenance and reducing duplication.

---

Note:
No application code was changed; this update is limited to CI/CD automation via GitHub Actions.

[Evanfeenstra]

The code is now available—please review it directly in the codespace.

Code

[Evanfeenstra]

The changes are ready for review.

[tomsmith8]

damn, forgot to pass codespaceurl

[stakgraph]

🤖 Processing your request... Stakwork run

I've received your message and started working on it. You'll receive a detailed response shortly.

[stakgraph]

Summary

Stakgraph will create a new GitHub Action workflow to automatically trigger the Swarm /sync endpoint whenever there are updates to the master branches of both the sphinx-tribes (backend) and sphinx-tribes-frontend (frontend) repositories. This ensures both codebases are kept in sync via Swarm, using secure authentication and the required parameters.

---

Planned Changes

• Add GitHub Action Workflow:
  • New workflow file: .github/workflows/sync-codebase.yml
  • Trigger: On push to master branch of either repository
• Automate Swarm Sync Call:
  • Use curl to send a GET request to the Swarm /sync endpoint
  • Pass both repository URLs in the source_link parameter (comma-separated)
  • Include pat parameter for authentication
  • Use x-api-token header with secret

---

Files/Areas Affected

• .github/workflows/sync-codebase.yml (new file)
• GitHub repository secrets:
  • SWARM_API_KEY
  • TRIBES_GITHUB_PAT

---

Notes

• Only triggers on master branch updates
• Ensures both backend and frontend repositories are synchronized via Swarm
• Uses secure secrets for authentication in the workflow