fix: Add Railway deployment configs and GitHub workflows

- Add Railway configuration (railway.toml)
- Add GitHub Actions workflows
  - Railway deployment automation
  - Python/Node.js testing
  - Health check monitoring
- Add GitHub templates (CODEOWNERS, PR template)
- Add requirements files if missing
- Standardize deployment across all services

This ensures consistent deployment patterns across the entire
BlackRoad OS infrastructure.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Alexa Louise
2025-12-10 15:35:09 -06:00
parent 5b8f5be59a
commit c00b6ee2a1
30 changed files with 2712 additions and 198 deletions

61
.github/workflows/stale.yml vendored Normal file
View File

@@ -0,0 +1,61 @@
# ============================================================================
# BlackRoad OS - Stale Issue/PR Management
# Copyright (c) 2025 BlackRoad OS, Inc. / Alexa Louise Amundson
# All Rights Reserved.
# ============================================================================
#
# Automatically marks and closes stale issues and PRs.
# ============================================================================
name: Stale
on:
schedule:
- cron: '0 0 * * *' # Daily at midnight
workflow_dispatch:
permissions:
issues: write
pull-requests: write
jobs:
stale:
name: Mark Stale Issues and PRs
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v9
with:
# Issue configuration
stale-issue-message: |
This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
If this issue is still relevant:
- Add a comment explaining the current status
- Remove the `stale` label
Thank you for your contributions to BlackRoad OS!
stale-issue-label: 'stale'
days-before-issue-stale: 60
days-before-issue-close: 14
exempt-issue-labels: 'pinned,security,critical,in-progress'
# PR configuration
stale-pr-message: |
This pull request has been automatically marked as stale because it has not had recent activity.
It will be closed in 7 days if no further activity occurs.
If this PR is still needed:
- Rebase on the latest main branch
- Address any review feedback
- Add a comment with status update
Thank you for your contributions!
stale-pr-label: 'stale'
days-before-pr-stale: 30
days-before-pr-close: 7
exempt-pr-labels: 'pinned,security,do-not-close'
# General
remove-stale-when-updated: true
operations-per-run: 100