I’m pleased to announce significant enhancements to the settings system that provide users with unprecedented control over their workflow configuration. These improvements introduce a more sophisticated settings hierarchy, personal repository customization capabilities, and enhanced flexibility that adapts to your unique needs.

Enhanced Settings Hierarchy and Override Mechanisms

The new settings system introduces a powerful hierarchical structure that allows for intelligent configuration management across different levels of your workflow. This enhancement ensures that settings can be both globally consistent and locally customized as needed.

Key Benefits of the Enhanced Hierarchy

  • Intelligent Override System: Settings at more specific levels automatically override broader configurations, allowing for precise control where needed
  • Context-Aware Configuration: Different contexts can have their own specialized settings while inheriting from base configurations
  • Reduced Configuration Duplication: Common settings can be defined once and inherited, reducing maintenance overhead
  • Predictable Behavior: Clear precedence rules ensure settings behave consistently across your workflow

This hierarchical approach means you can establish sensible defaults while still having the flexibility to make targeted adjustments for specific scenarios without affecting your overall configuration.

Personal Repository Customization Capabilities

One of the most powerful new features is the ability to customize settings at the personal repository level. This enhancement recognizes that different projects, contexts, or repositories often require their own unique configurations while still benefiting from shared baseline settings.

What Personal Repository Customization Enables

  • Project-Specific Workflows: Tailor your task management approach for different projects or contexts
  • Team Collaboration: Share repository-specific settings while maintaining personal preferences
  • Contextual Adaptation: Automatically apply the right settings based on the repository you’re working in
  • Granular Control: Fine-tune configurations for specific use cases without affecting other workflows

This capability is particularly valuable for users who work across multiple projects, collaborate with different teams, or need to maintain distinct workflows for various aspects of their work and personal life.

Improved Configuration Flexibility

The enhanced settings system provides unprecedented flexibility in how you configure and manage your workflow. This improvement focuses on making the system more adaptable to diverse working styles and preferences.

Enhanced Flexibility Features

  • Modular Configuration: Settings can be organized and managed in logical groups
  • Conditional Settings: Apply different configurations based on specific conditions or contexts
  • Dynamic Configuration: Settings can adapt based on your current workflow state
  • Extensible Framework: Easy to add new configuration options as your needs evolve

This flexibility ensures that the settings system can grow and adapt with you, providing a solid foundation that supports both your current needs and future requirements.

Better User Experience for Settings Management

Managing settings should be intuitive and straightforward. The enhanced system includes several improvements focused on making configuration management more user-friendly and efficient.

User Experience Improvements

  • Clearer Organization: Settings are logically grouped and easier to navigate
  • Intuitive Defaults: Sensible out-of-the-box configurations that work for most users
  • Helpful Validation: Clear feedback when configurations might cause issues
  • Simplified Maintenance: Easier to update and manage settings over time

These improvements reduce the cognitive load associated with configuration management, allowing you to focus on your work rather than on managing your settings.

Spotlight: Default Board Feature

As part of these broader settings enhancements, i’ve introduced a particularly useful feature that exemplifies the power of the new system: the default board functionality for todo list management in multi-board workflows.

Details of the Default Board Feature

The default board feature introduces intelligent card routing specifically for the todo list (Doing Today list) that automatically assigns cards to a predefined board when no board prefix is detected. This eliminates the need to manually specify board names for routine tasks while maintaining the flexibility to override when needed.

The implementation centers around two key settings in your doingSettings.md:

  • Default Board Name: Specifies the fallback board for unassigned cards in your todo list
  • Prefix Cards With Board Name: Controls whether board names are prepended to card titles

Context and Benefits

In multi-board workflows, users often have a primary board where most routine tasks belong. Previously, every card in your todo list required explicit board prefixing, creating unnecessary friction for common tasks. The default board feature addresses this by establishing a smart default while preserving the power of board-specific routing when needed.

This enhancement is particularly valuable for users who:

  • Work with a primary “Personal” or “General” board for most tasks
  • Use specialized boards for specific projects or contexts
  • Want to reduce cognitive overhead when creating new tasks in their todo list
  • Prefer cleaner card names without repetitive board prefixes

How to Use the Default Board Feature

The default board feature works automatically in the background once configured. Here’s how to set it up and use it effectively:

Configuration

In your settings/doingSettings.md file, configure these key settings:

* Default Board Name: Focus
* Prefix Cards With Board Name: true

Basic Usage

Without board prefix (uses default):

Buy groceries
Call dentist
Review project proposal

These cards in your todo list automatically route to your “Focus” board.

With explicit board prefix (overrides default):

━❱➤ Work: Schedule team meeting
━❱➤ Projects: Update website design

These cards route to their specified boards.

Practical Examples

Example 1: Personal Task Management

Doing Today list contains:
- Morning exercise
- Read 20 pages
- Work: Prepare presentation
- Buy birthday gift

Result: “Morning exercise”, “Read 20 pages”, and “Buy birthday gift” go to Focus board, while “Prepare presentation” goes to Work board.

Example 2: Mixed Project Workflow

Doing Today list contains:
- Review code changes
- Projects: Update documentation
- Client meeting notes
- Home: Fix leaky faucet

Result: Cards without prefixes go to Focus board, while explicitly prefixed cards go to their respective boards.

Advanced Configuration

For different workflows, you can adjust the settings:

Minimal prefixing:

* Default Board Name: General
* Prefix Cards With Board Name: false

This keeps card names clean while still routing to the correct boards.

Project-focused workflow:

* Default Board Name: Projects
* Prefix Cards With Board Name: true

This makes Projects the default destination for most tasks in your todo list.

Important Notes

  • This feature only applies to the todo list (Doing Today list) functionality
  • It does not affect general board routing or other Stream features
  • Cards are only processed when the checkdoingcards.js script runs
  • If the default board doesn’t exist, cards will be marked with a red cross symbol

Enhanced Repository Commit Reporting: Multi-Branch Support and Visibility

As part of the broader settings system enhancements, I’ve implemented significant improvements to the repository commit reporting functionality that transforms how users monitor and track changes across multiple repositories and branches. These enhancements solve a critical problem: the inability to track specific branches instead of just the current branch, providing unprecedented visibility into development activity.

The Problem We Solved

Previously, the repository monitoring system was limited to tracking commits only from the current branch of each repository. This created significant blind spots for developers who work across multiple branches or need to monitor specific development streams like dev, staging, or feature branches. Users couldn’t easily answer questions like “What’s happening in our development branch?” or “Are there commits in the staging branch I should review?”

Technical Implementation Highlights

The enhanced system introduces sophisticated branch management capabilities that seamlessly integrate with the existing repository monitoring workflow:

Multi-Branch Configuration Support

The system now supports both single and comma-separated branch configurations in your repos.md file:

## Single branch configuration
* branch:dev

## Multi-branch configuration
* branch:dev,main,staging

This flexibility allows you to monitor exactly the branches that matter to your workflow, whether you’re tracking a single development branch or multiple release streams simultaneously.

Intelligent Branch Switching and Restoration

The core enhancement includes automatic branch switching with guaranteed restoration to the original branch. The system:

  1. Preserves Original State: Captures the current branch before any operations
  2. Sequential Processing: Processes each branch in order, updating and fetching commits
  3. Automatic Restoration: Returns the repository to its original branch state
  4. Error Resilience: Continues processing other branches even if one fails

Enhanced Visibility and Logging

The new system provides comprehensive logging that makes repository operations transparent and debuggable:

📍 Original branch for infinikan: main
🔄 Processing 2 branch(es) for infinikan: dev, main
🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀
🔀 PROCESSING BRANCH: infinikan → dev
🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀🔀
🔄 Switching infinikan from main to dev
📝 Found 3 commits in infinikan (dev)
📄 Fix authentication flow
📄 Add user profile validation
📄 Update API documentation
🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙
🔙 RESTORING: infinikan returning to original branch main
🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙🔙
✅ Successfully restored infinikan to original branch main

Key Features and Benefits

Optional Branch Configuration

The branch configuration is completely optional. Repositories without a branch setting continue to work as before, monitoring the current branch. This backward compatibility ensures existing workflows remain unaffected while providing powerful new capabilities when needed.

Enhanced Trello Card Creation

The system creates rich, informative Trello cards that include:

  • Branch Operations Summary: Detailed statistics about multi-branch processing
  • Per-Branch Commit Breakdown: Commits organized by branch with clear separation
  • Processing Statistics: Total branches processed, switches performed, and success rates
  • Error Reporting: Clear visibility into any branch-specific issues

Robust Error Handling

The system gracefully handles various error scenarios:

  • Missing Branches: Automatically fetches branches from remote if not available locally
  • Network Issues: Continues processing other repositories if one fails
  • Detached HEAD State: Provides clear error messages for problematic repository states
  • Permission Issues: Logs access problems without stopping the entire process

Practical Configuration Examples

Example 1: Development Branch Monitoring

## Infinikan Project
* basePath:/Users/fred/dev/infinikan
* title:Infinite Kanban board
* auto sync:true
* rank: 3
* user name:superfred
* user email:fred@bloggs.com
* branch:dev,main
* Clone Url: git@github.com-superfred:superfred/infinikan.git

This configuration monitors both the development and main branches, providing visibility into both active development and stable releases.

Example 2: Release Pipeline Tracking

## Critical Production App
* basePath:/Users/fred/dev/production-app
* title:Production Application
* auto sync:true
* rank: 1
* branch:staging,main,hotfix
* Clone Url: git@github.com-company_github:company/production-app.git

This setup tracks the complete release pipeline from staging through production to emergency hotfixes.

Example 3: Mixed Workflow

## Legacy Project (current branch only)
* basePath:/Users/fred/dev/legacy-app
* title:Legacy Application
* auto sync:true
* rank: 5
* Clone Url: git@github.com-company_github:company/legacy-app.git

## Modern Project (multi-branch)
* basePath:/Users/fred/dev/modern-app
* title:Modern Application
* auto sync:true
* rank: 1
* branch:dev,feature/api-v2,main
* Clone Url: git@github.com-company_github:company/modern-app.git

This demonstrates how you can mix traditional single-branch monitoring with advanced multi-branch tracking in the same workflow.

Benefits for Multi-Repository Users

The enhanced repository commit reporting provides significant advantages for users managing multiple repositories:

Comprehensive Visibility

  • Complete Development Picture: See activity across all important branches, not just the current one
  • Release Pipeline Awareness: Monitor commits moving through staging, testing, and production branches
  • Feature Branch Tracking: Keep an eye on specific feature branches without switching contexts

Improved Workflow Efficiency

  • Reduced Context Switching: No need to manually switch branches to check for commits
  • Automated Monitoring: Set it once and get comprehensive reports automatically
  • Time-Saving: Eliminates manual branch checking across multiple repositories

Enhanced Team Collaboration

  • Better Coordination: Team members can see activity across all relevant branches
  • Release Planning: Clear visibility into what’s ready for release across different branches
  • Code Review Awareness: Immediate notification when commits are pushed to review branches

Technical Excellence

The implementation demonstrates several software engineering best practices:

  • Atomic Operations: Each repository is processed independently with guaranteed state restoration
  • Comprehensive Logging: Every operation is logged for transparency and debugging
  • Graceful Degradation: The system continues working even when individual repositories or branches fail
  • Performance Optimization: Sequential processing prevents resource conflicts while maintaining efficiency

This enhancement represents a significant leap forward in repository monitoring capabilities, providing the visibility and control needed for modern development workflows while maintaining the simplicity and reliability that users expect from the Stream system.

Summary

The enhanced settings system represents a significant leap forward in workflow customization and management. These improvements provide:

  • Hierarchical Configuration: Intelligent override mechanisms for precise control
  • Personal Repository Customization: Tailored settings for different projects and contexts
  • Enhanced Flexibility: Adaptable configuration that grows with your needs
  • Improved User Experience: Intuitive management and sensible defaults
  • Powerful Features: Like the default board functionality that streamline common workflows
  • Enhanced Repository Commit Reporting: Multi-branch support with automatic switching and comprehensive visibility

By combining these enhancements, i’ve created a settings system that truly adapts to your unique workflow rather than forcing you to adapt to it. Whether you’re managing personal tasks, work projects, or a combination of both, the enhanced settings system helps you focus on what matters most rather than on configuration management.

The default board feature and enhanced repository commit reporting are just two examples of how these enhancements translate into tangible benefits for users. The multi-branch support solves a critical problem for developers who need to monitor specific branches rather than just the current branch, providing unprecedented visibility into development activity across multiple repositories and branches.

As I continue to build on this foundation, you can expect even more powerful customization options that make your workflow more efficient and enjoyable.