Skip to content

Missing ignore rules for non-coding files (README, LICENSE, .gitignore, etc.) #2

@whaiman

Description

@whaiman

Title
No ignore mechanism for non-source files skews project statistics

Description

DevLedger currently records activity for all files without distinction.

This leads to distorted statistics when working with files such as:

  • README.md
  • LICENSE
  • .gitignore
  • generated YAML/CI files
  • configuration files
  • documentation files

Editing or generating these files contributes to:

  • total coding time
  • language statistics
  • behavior analysis

This produces misleading reports, especially for small projects where documentation or config edits can dominate the stats.

Why this matters

DevLedger aims to provide a reliable representation of coding activity.
Including non-source and generated files pollutes:

  • per-language metrics
  • time distribution
  • behavior analysis signals

For example, generating or editing a large README can appear as significant Markdown “coding time”.

Expected behavior

DevLedger should support an ignore mechanism similar to .gitignore, for example:

.devledgerignore

Example:

README.md
LICENSE
.gitignore
*.yml
*.yaml
docs/**

These files should be excluded from:

  • time tracking
  • language stats
  • behavior analysis

Acceptance criteria

  • Support for .devledgerignore
  • Glob pattern matching
  • Ignored files do not produce events for aggregation
  • Default built-in ignore list for common non-source files (README, LICENSE, etc.)

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions