feat: comprehensive CI formatting solution and development automation

- Add automated development environment setup (.github/setup-dev.sh)
- Add pre-commit hook for automatic code formatting (.github/pre-commit-hook.sh)
- Enhance CI workflow with base build validation and optimized build process
- Update copilot instructions with stronger formatting enforcement and dev environment docs
- Add comprehensive development section to README with setup instructions
- Update .gitignore to whitelist .github development tools
- Fix formatting issues in src/main.rs (trailing whitespace, spacing)

This multi-layered solution prevents CI formatting failures through:
1. Automatic pre-commit formatting hooks
2. Enhanced copilot instruction enforcement
3. Clear developer setup and workflow documentation
4. Improved CI validation and error reporting

Author: nerdCopter

.github/copilot-instructions.md

@@ -23,6 +23,11 @@
   - Use date-prefixed, uppercase filenames (e.g., `2025-06-25_SUMMARY.md`).
   - List new files when created.
 
+## Development Environment
+- **Setup Script:** Use `.github/setup-dev.sh` for automated development environment setup
+- **Pre-commit Hook:** `.github/pre-commit-hook.sh` automatically formats code before commits
+- **CI Compliance:** All changes must pass the GitHub Actions CI pipeline
+
 ## Goals & Resources
 - **Goals:** Reference project goals in `GOALS.md` and request clarification if needed.
 - **Source Code Resources:**  
@@ -40,7 +45,7 @@
   - `cargo test --features=cli --verbose` passes.
   - `cargo build --release` passes with no errors or warnings.
 - **Files to Commit:**
-  - Only `src/**/*.rs`, `Cargo.*`, `README.md`, `OVERVIEW.md` and `.gitignore` — never `git add .` or `git add -A`.
+  - Only `src/**/*.rs`, `Cargo.*`, `README.md`, `OVERVIEW.md`, `.gitignore`, and `.github/**` — never `git add .` or `git add -A`.
   - Follow `.gitignore`.
 - **User Confirmation:** Ask user before committing.
 - **Commit Message:**
@@ -51,7 +56,9 @@
 ## Mandatory Checks
 - **BEFORE ANY CODE CHANGES:** Always run `cargo clippy --all-targets --all-features -- -D warnings` to catch ALL issues.
 - **BEFORE ANY CODE CHANGES:** Always run `cargo fmt --all -- --check` to ensure formatting compliance.
+- **IMMEDIATE FORMATTING FIX:** If `cargo fmt --all -- --check` fails, IMMEDIATELY run `cargo fmt --all` to fix formatting.
 - **NO OPTIONAL FEATURES ERRORS:** All feature combinations must compile without errors.
 - **NO FORMATTING VIOLATIONS:** Code must pass `cargo fmt --all -- --check` without any formatting issues.
 - **STRICT COMPLIANCE:** Never skip clippy checks or formatting checks. Never allow warnings to pass.
-- **IMMEDIATE FORMATTING:** Apply `cargo fmt --all` immediately if formatting check fails.
+- **AUTOMATIC FORMATTING:** ALWAYS run `cargo fmt --all` after making ANY code changes before moving to next steps.
+- **DOUBLE CHECK FORMATTING:** After running `cargo fmt --all`, ALWAYS verify with `cargo fmt --all -- --check` before proceeding.

.github/instructions/rust-project.instructions.md

@@ -0,0 +1,48 @@
+# Copilot Instructions for RUST Project
+
+## General
+- **Entry Point:** Maintain source as `src/main.rs`.
+- **Comments:**  
+  - Do not remove or modify comments unless the related code is changed.
+  - Only add comments that explain code functionality; no AI instructional comments.
+- **No External Binaries:** Never embed or call external binaries from RUST code.
+- **Temporary Files:** Use `_temp.rs` extension for any temporary `.rs` files.
+- **Build Quality:** Ensure `cargo build --release` has no errors or warnings.
+- **File Editing:** Always edit files inline; do not use `cat` to write to files.
+
+## Algorithms
+- **Method Selection:**  
+  - When choosing math or scientific methods, compare alternatives for accuracy and efficiency.
+  - Fact-check method decisions.
+
+## Documentation
+- **Readme:** Maintain a proper `README.md` file.
+- **Overview** Maintain a proper `OVERVIEW.md` file
+- **Summaries:**  
+  - Output final summaries to `./INFORMATION/*.md` (not in git).
+  - Use date-prefixed, uppercase filenames (e.g., `2025-06-25_SUMMARY.md`).
+  - List new files when created.
+
+## Goals & Resources
+- **Goals:** Reference project goals in `GOALS.md` and request clarification if needed.
+- **Source Code Resources:**  
+  - Primary: [blackbox_decode (blackbox-tools)](https://github.com/betaflight/blackbox-tools/blob/master/src/blackbox_decode.c)
+  - Fallback: [blackbox-log-viewer (BBE)](https://github.com/betaflight/blackbox-log-viewer/blob/master/src/flightlog.js)
+
+## Data Validation
+- **REQUIRED:**  The CSV output must precisely match the format and header order of blackbox_decode CSV files.
+
+## Committing Rules
+- **Commit Conditions:** Only commit if:
+  - `cargo clippy -- -D warnings` passes.
+  - `cargo fmt --all -- --check` passes.
+  - `cargo test --verbose` passes.
+  - `cargo test --features=cli --verbose` passes.
+- **Files to Commit:**
+  - Only `src/**/*.rs`, `Cargo.*`, `README.md`, `OVERVIEW.md` and `.gitignore` — never `git add .` or `git add -A`.
+  - Follow `.gitignore`.
+- **User Confirmation:** Ask user before committing.
+- **Commit Message:**
+  - Check `git diff --cached` before committing.
+  - Use concise commit messages and descriptions.
+  - Use `feat:`, `fix:`, `docs:` where applicable.

.github/pre-commit-hook.sh

@@ -0,0 +1,30 @@
+#!/bin/bash
+# Pre-commit hook to automatically format Rust code
+# Install this by copying to .git/hooks/pre-commit and making it executable
+
+echo "Running pre-commit formatting check..."
+
+# Check if cargo fmt is available
+if ! command -v cargo &> /dev/null; then
+    echo "❌ cargo not found. Please install Rust toolchain."
+    exit 1
+fi
+
+# Format the code
+echo "🔧 Auto-formatting Rust code..."
+cargo fmt --all
+
+# Check if there are any changes after formatting
+if ! git diff --exit-code --quiet; then
+    echo "✅ Code has been automatically formatted."
+    echo "📝 The following files were formatted:"
+    git diff --name-only
+    echo ""
+    echo "🔄 Please review the changes and commit again."
+    echo "   The formatting has been applied automatically."
+    exit 1
+else
+    echo "✅ Code formatting is already correct."
+fi
+
+echo "✅ Pre-commit checks passed!"

.github/setup-dev.sh

@@ -0,0 +1,63 @@
+#!/bin/bash
+# Developer setup script for bbl_parser project
+# This script sets up the development environment with proper formatting checks
+
+set -e
+
+echo "🚀 Setting up bbl_parser development environment..."
+
+# Check if we're in a git repository
+if [ ! -d ".git" ]; then
+    echo "❌ Error: This script must be run from the root of the git repository."
+    exit 1
+fi
+
+# Install pre-commit hook
+echo "📥 Installing pre-commit hook for automatic formatting..."
+if [ -f ".github/pre-commit-hook.sh" ]; then
+    cp .github/pre-commit-hook.sh .git/hooks/pre-commit
+    chmod +x .git/hooks/pre-commit
+    echo "✅ Pre-commit hook installed successfully."
+else
+    echo "⚠️  Pre-commit hook not found. Skipping..."
+fi
+
+# Run initial formatting check
+echo "🔧 Running initial formatting check..."
+if ! cargo fmt --all -- --check; then
+    echo "⚠️  Code needs formatting. Applying automatic formatting..."
+    cargo fmt --all
+    echo "✅ Code has been formatted."
+else
+    echo "✅ Code formatting is already correct."
+fi
+
+# Run clippy check
+echo "🔍 Running clippy check..."
+if ! cargo clippy --all-targets --all-features -- -D warnings; then
+    echo "❌ Clippy found issues. Please fix them before continuing."
+    exit 1
+else
+    echo "✅ Clippy check passed."
+fi
+
+# Run tests
+echo "🧪 Running tests..."
+if ! cargo test --verbose; then
+    echo "❌ Tests failed. Please fix them before continuing."
+    exit 1
+else
+    echo "✅ All tests passed."
+fi
+
+echo ""
+echo "🎉 Development environment setup complete!"
+echo ""
+echo "📋 Remember to always run these commands before committing:"
+echo "   cargo fmt --all                                     # Format code"
+echo "   cargo clippy --all-targets --all-features -- -D warnings  # Check for issues"
+echo "   cargo test --verbose                                # Run tests"
+echo "   cargo test --features=cli --verbose                 # Run CLI tests"
+echo "   cargo build --release                               # Build release"
+echo ""
+echo "🔧 The pre-commit hook will automatically format your code on each commit."

.github/workflows/ci.yml

@@ -44,6 +44,9 @@ jobs:
       - name: Check documentation
         run: cargo doc --no-deps --all-features
 
+      - name: Check base build
+        run: cargo build --release
+
   test:
     name: Test
     runs-on: ${{ matrix.os }}
@@ -115,7 +118,7 @@ jobs:
           key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
 
       - name: Build release binary
-        run: cargo build --release --features=cli
+        run: cargo build --release
 
       - name: Upload binary artifact
         uses: actions/upload-artifact@v4

.gitignore

@@ -18,3 +18,12 @@
 !examples/
 !examples/*.rs
 !examples/README.md
+
+# Whitelist .github directory and development tools
+!.github/
+!.github/workflows/
+!.github/workflows/*.yml
+!.github/instructions/
+!.github/instructions/*.md
+!.github/*.md
+!.github/*.sh

README.md

@@ -402,6 +402,63 @@ Event parsing uses the official Betaflight FlightLogEvent enum:
 - Processes files that may cause external decoders to fail
 - Zero external dependencies - no blackbox_decode tools required
 
+## Development
+
+### Setting Up Development Environment
+
+To set up your development environment with proper formatting and pre-commit hooks:
+
+```bash
+# Clone and setup
+git clone <repository-url>
+cd bbl_parser
+
+# Run setup script (optional but recommended)
+chmod +x .github/setup-dev.sh
+./.github/setup-dev.sh
+```
+
+### Required Commands Before Committing
+
+**⚠️ IMPORTANT**: Always run these commands before committing to avoid CI failures:
+
+```bash
+# 1. Format code (REQUIRED)
+cargo fmt --all
+
+# 2. Check formatting compliance
+cargo fmt --all -- --check
+
+# 3. Check for clippy warnings (treated as errors)
+cargo clippy --all-targets --all-features -- -D warnings
+
+# 4. Run all tests
+cargo test --verbose
+cargo test --features=cli --verbose
+
+# 5. Verify release build
+cargo build --release
+```
+
+### Pre-commit Hook (Recommended)
+
+Install the pre-commit hook to automatically format code:
+
+```bash
+cp .github/pre-commit-hook.sh .git/hooks/pre-commit
+chmod +x .git/hooks/pre-commit
+```
+
+This will automatically run `cargo fmt --all` before each commit and prevent commits with formatting issues.
+
+### CI Requirements
+
+The GitHub Actions CI enforces strict formatting and code quality:
+- **Formatting**: Must pass `cargo fmt --all -- --check`
+- **Linting**: Must pass `cargo clippy --all-targets --all-features -- -D warnings` 
+- **Testing**: Must pass all tests including CLI features
+- **Building**: Must build successfully on Ubuntu, Windows, and macOS
+
 ## Dependencies
 
 - `clap` (v4.0+) - CLI parsing

src/main.rs

@@ -1116,13 +1116,13 @@ fn should_skip_export(log: &BBLLog, force_export: bool) -> (bool, String) {
 /// Returns true if the log appears to be a static ground test (minimal movement)
 fn has_minimal_gyro_activity(log: &BBLLog) -> (bool, f64) {
     // Conservative thresholds to avoid false-skips
-    const MIN_SAMPLES_FOR_ANALYSIS: usize = 15; // Reduced for limited sample data 
+    const MIN_SAMPLES_FOR_ANALYSIS: usize = 15; // Reduced for limited sample data
     const VERY_LOW_GYRO_VARIANCE_THRESHOLD: f64 = 0.3; // More aggressive threshold for ground test detection
-    
+
     let mut gyro_x_values = Vec::new();
     let mut gyro_y_values = Vec::new();
     let mut gyro_z_values = Vec::new();
-    
+
     // First try to use debug_frames if available (contains more comprehensive data)
     if let Some(debug_frames) = &log.debug_frames {
         // Collect gyro data from I and P frames in debug_frames
@@ -1142,7 +1142,7 @@ fn has_minimal_gyro_activity(log: &BBLLog) -> (bool, f64) {
             }
         }
     }
-    
+
     // Fallback to sample_frames if debug_frames not available or insufficient data
     if gyro_x_values.len() < MIN_SAMPLES_FOR_ANALYSIS {
         for frame in &log.sample_frames {
@@ -1157,23 +1157,23 @@ fn has_minimal_gyro_activity(log: &BBLLog) -> (bool, f64) {
             }
         }
     }
-    
+
     // Need sufficient data points for reliable analysis
     if gyro_x_values.len() < MIN_SAMPLES_FOR_ANALYSIS {
         return (false, 0.0); // Not enough data, don't skip (conservative approach)
     }
-    
+
     // Calculate variance for each axis
     let variance_x = calculate_variance(&gyro_x_values);
-    let variance_y = calculate_variance(&gyro_y_values);  
+    let variance_y = calculate_variance(&gyro_y_values);
     let variance_z = calculate_variance(&gyro_z_values);
-    
+
     // Use the maximum variance across all axes
     let max_variance = variance_x.max(variance_y).max(variance_z);
-    
+
     // Very conservative: only skip if ALL axes show extremely low variance
     let is_minimal = max_variance < VERY_LOW_GYRO_VARIANCE_THRESHOLD;
-    
+
     (is_minimal, max_variance)
 }
 
@@ -1182,12 +1182,10 @@ fn calculate_variance(values: &[f64]) -> f64 {
     if values.len() < 2 {
         return 0.0;
     }
-    
+
     let mean = values.iter().sum::<f64>() / values.len() as f64;
-    let variance = values.iter()
-        .map(|x| (x - mean).powi(2))
-        .sum::<f64>() / values.len() as f64;
-    
+    let variance = values.iter().map(|x| (x - mean).powi(2)).sum::<f64>() / values.len() as f64;
+
     variance
 }