Future Features: Nice to Have Ideas

[gjed]

Future Feature Ideas

This discussion collects potential features that would be nice to have but are lower priority than the current roadmap items. Feel free to comment with your thoughts, vote with reactions, or suggest additional ideas!

---

1. Web UI / Dashboard

A simple web interface to visualize managed repositories and their configurations.

Use cases:

• Quick overview of all managed repos and their settings
• Visual diff between YAML config and actual GitHub state
• Non-technical stakeholders can view (but not edit) configurations

Implementation ideas:

• Static site generated from YAML configs
• Simple React/Vue app reading from GitHub API
• Terraform output rendered as HTML

---

2. Slack/Teams Notifications

Alert on Terraform apply success/failure and other events.

Features:

• Notify on successful applies with summary of changes
• Alert on failures with error details
• Daily/weekly digest of managed repositories
• Drift detection alerts

Implementation:

• GitHub Action with Slack/Teams webhook
• Optional Lambda/Cloud Function for more complex notifications

---

3. Interactive Import Wizard

Improve the existing onboard-repos.sh script with an interactive CLI experience.

Features:

• Interactive prompts to select which repos to import
• Preview generated YAML before writing
• Detect existing settings and suggest group assignments
• Dry-run mode to see what would be imported
• Support for filtering (by topic, visibility, team, etc.)

Implementation:

• Python CLI with rich or inquirer for interactive UI
• Or a TUI (terminal UI) application

---

4. Multi-Organization Support

Manage multiple GitHub organizations from a single configuration.

Use cases:

• Companies with multiple orgs (e.g., main org + OSS org)
• MSPs managing client organizations
• Consistent policies across related organizations

Challenges:

• Multiple GitHub tokens/authentication
• Cross-org references (teams, users)
• State management complexity

Possible approach:

# config/organizations.yml
organizations:
  main-org:
    token: env:GITHUB_TOKEN_MAIN
    config_dir: ./config/main-org/
  
  oss-org:
    token: env:GITHUB_TOKEN_OSS
    config_dir: ./config/oss-org/

---

How to Contribute Ideas

1. React to features you find valuable (thumbs up, heart, etc.)
2. Comment with additional details, use cases, or implementation suggestions
3. Open an issue if you want to work on implementing any of these

---

Related Issues

See the current roadmap in the issues labeled enhancement:

• Feature: Branch protection/ruleset templates #2 - Branch protection templates
• Feature: Repository and organization secrets management #3 - Secrets management
• Feature: Webhooks configuration #4 - Webhooks configuration
• Feature: GitHub Actions permissions configuration #5 - GitHub Actions permissions
• Feature: Dependabot and Renovate configuration management #6 - Dependabot/Renovate configuration
• Feature: Issue and PR templates management #7 - Issue/PR templates
• Feature: Default branch files management #8 - Default branch files
• Feature: Configuration drift detection #9 - Drift detection
• Feature: Example CI/CD workflows in ci/ folder #10 - Example CI workflows