Merge pull request #47 from Githubguy132010/update-documentation

📚 Documentation Update

Author: Githubguy132010

workflows_doc.md

@@ -1,91 +1,65 @@
-# Workflow Documentation
-
-## Overview
-This document details the automated workflows used in the Arch Linux Without the Beeps project.
-
-## Package Update Workflow
-
-### Purpose
-The package update workflow (`update-packages.yaml`) automatically checks for package updates and creates pull requests when updates are available.
-
-### Workflow Triggers
-- Scheduled: Runs daily at 2 AM UTC
-- Manual: Can be triggered via GitHub Actions interface
-
-### Process Steps
-1. **Environment Setup**
-   - Checks out repository
-   - Sets up Docker container
-   - Initializes package cache
-
-2. **Package Verification**
-   - Validates current package list
-   - Checks for available updates
-   - Verifies package integrity
-
-3. **Update Process**
-   - Creates update manifest
-   - Generates package changelog
-   - Creates pull request with updates
-
-### Error Handling
-- Implements retry logic for failed downloads
-- Validates package checksums
-- Maintains build logs
-- Cleans up temporary files
-
-## Build Process
-
-### ISO Build Steps
-1. **Preparation**
-   - Validate configurations
-   - Check system requirements
-   - Prepare build environment
-
-2. **Build Process**
-   - Generate ISO
-   - Verify system configurations
-   - Perform integrity checks
-
-3. **Validation**
-   - Check ISO checksums
-   - Verify beep configurations
-   - Test critical components
-
-### Safety Measures
-- Automated testing procedures
-- Rollback capabilities
-- Configuration backups
-- Build artifact validation
-
-## Maintenance
-
-### Cache Management
-- Monthly cache rotation
-- Automated cleanup procedures
-- Storage optimization
-
-### Monitoring
-- Build status tracking
-- Error reporting
-- Performance metrics
-
-## Troubleshooting
-
-### Common Issues
-1. **Build Failures**
-   - Check system resources
-   - Verify package availability
-   - Review error logs
-
-2. **Package Conflicts**
-   - Check dependency tree
-   - Verify package versions
-   - Review conflict reports
-
-### Recovery Procedures
-1. Clear build cache
-2. Reset Docker environment
-3. Verify package integrity
-4. Check system configurations
+## 🔄 Automated Workflows
+
+This project uses the following GitHub Actions workflows:
+
+### Build ISO
+
+File: `build-and-release.yaml`
+
+Triggered by:
+- 🔘 Manual trigger
+- ⏰ Scheduled: `0 0 * * *`
+- 📤 Push to repository
+
+### Build and Save ISO
+
+File: `build-and-save.yaml`
+
+Triggered by:
+- 🔘 Manual trigger
+- ⏰ Scheduled: `0 0 * * *`
+
+### Validate and Test Build
+
+File: `build-check.yaml`
+
+Triggered by:
+- 🔘 Manual trigger
+- ⏰ Scheduled: `0 0 * * *`
+- 🔄 Pull request
+
+### Create/Update Release
+
+File: `create-release.yaml`
+
+Triggered by:
+- 🔘 Manual trigger
+- 📤 Push to repository
+
+### Check to make sure Dockerfile works
+
+File: `dockerfile-check.yaml`
+
+Triggered by:
+- 🔘 Manual trigger
+- ⏰ Scheduled: ``
+- 🔄 Pull request
+
+### Update Documentation
+
+File: `update-docs.yaml`
+
+Triggered by:
+- 🔘 Manual trigger
+- ⏰ Scheduled: `" -f2)`
+- 📤 Push to repository
+- 🔄 Pull request
+
+### Update Packages
+
+File: `update-packages.yaml`
+
+Triggered by:
+- 🔘 Manual trigger
+- ⏰ Scheduled: `0 2 * * *`