chore: Bump version to 3.1.0 and update documentation

- Update VERSION file from 3.0.0 to 3.1.0
- Update CHANGELOG.md with v3.1.0 release notes
  - Document renamed/moved files support feature
  - Note that this fixes issue #15
  - Document test infrastructure improvements
  - Document 100% code coverage achievement
- Update README.md
  - Include renamed files (R) in the main description
  - Add examples of renamed file output in Try it section
  - Update gem build instructions to reference v3.1.0
  - Update repository URLs from knugie to wteuber
- Add missing copyright year updates in LICENSE files

Author: wteuber

CHANGELOG.md

@@ -7,12 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.1.0] - 2025-01-16
+
 ### Added
+- Proper support for renamed/moved files in git status
+  - Same directory renames show as: `file.rb -> new_file.rb (R+)`
+  - Cross-directory moves show full destination path: `file.rb -> lib/file.rb (R+)`
+  - Maintains correct tree structure showing original file location
 - RuboCop code style checks integrated into test suite
 - SimpleCov code coverage analysis
   - Coverage reports generated in `coverage/` directory
+  - HTML and JSON format coverage reports
   - Tests fail if coverage drops
   - Can be disabled with `COVERAGE=false` environment variable
+- Comprehensive test coverage for GitStatusTree class
+- Test coverage for Node status methods (modified?, added?, etc.)
+- Test coverage for NodesCollection comparison and validation methods
+- Code coverage improved from 87.73% to 100%
+
+### Fixed
+- Fixed incorrect tree display for renamed files that previously showed duplicated path structure ([#15](https://github.com/wteuber/git-status-tree/issues/15))
 
 ## [3.0.0] - 2025-06-25
 
@@ -65,8 +79,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Fixed
 - "Try it" section in README documentation
 
-[Unreleased]: https://github.com/knugie/git-status-tree/compare/v3.0.0...HEAD
-[3.0.0]: https://github.com/knugie/git-status-tree/compare/v2.0.0...v3.0.0
-[2.0.0]: https://github.com/knugie/git-status-tree/compare/v1.0.1...v2.0.0
-[1.0.1]: https://github.com/knugie/git-status-tree/compare/v1.0.0...v1.0.1
-[1.0.0]: https://github.com/knugie/git-status-tree/releases/tag/v1.0.0 
+[Unreleased]: https://github.com/wteuber/git-status-tree/compare/v3.1.0...HEAD
+[3.1.0]: https://github.com/wteuber/git-status-tree/compare/v3.0.0...v3.1.0
+[3.0.0]: https://github.com/wteuber/git-status-tree/compare/v2.0.0...v3.0.0
+[2.0.0]: https://github.com/wteuber/git-status-tree/compare/v1.0.1...v2.0.0
+[1.0.1]: https://github.com/wteuber/git-status-tree/compare/v1.0.0...v1.0.1
+[1.0.0]: https://github.com/wteuber/git-status-tree/releases/tag/v1.0.0 

LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2013 Wolfgang Teuber, https://github.com/knugie/git-status-tree
+Copyright (c) 2013 Wolfgang Teuber, https://github.com/wteuber/git-status-tree
 You may use git-status-tree under the terms of either the MIT License
 or the GNU General Public License (GPL) Version 2.
 

MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2013 Wolfgang Teuber, https://github.com/knugie/git-status-tree
+Copyright (c) 2013 Wolfgang Teuber, https://github.com/wteuber/git-status-tree
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

README.md

@@ -2,13 +2,14 @@
 
 # git-status-tree
 
-git-status-tree (https://github.com/knugie/git-status-tree) is a command line tool that  
+git-status-tree (https://github.com/wteuber/git-status-tree) is a command line tool that  
 helps you keeping track of changes in your git repository. Similar to the `tree` command  
 (https://github.com/nodakai/tree-command), git-status-tree recursively lists directories  
 and files. Run `git tree` in the command line to list all files in your git repository that are  
-untracked (?) or have been added (A), modified (M) or deleted (D). The colored output  
+untracked (?), have been added (A), modified (M), deleted (D), or renamed (R). The colored output  
 shows whether a file has been added/staged (green)(+) or not (red). The current status  
-of each file is appended to it.
+of each file is appended to it. For renamed files, the tree structure shows the original  
+location with an arrow pointing to the new name or path.
 
 See [CHANGELOG.md](CHANGELOG.md) for a list of changes between versions.
 ___
@@ -47,7 +48,7 @@ git config --global status-tree.indent <indent>
 ## Try it
 ```
 gem install git-status-tree
-git clone https://github.com/knugie/git-status-tree.git
+git clone https://github.com/wteuber/git-status-tree.git
 cd git-status-tree
 echo "change" >> README.md
 echo "add untracked" > test/untracked.txt
@@ -64,6 +65,19 @@ git tree
 ├── DELETEME.txt (D+)
 └── README.md (M)
 
+# Example with renamed files
+git reset HEAD --hard
+git clean -xdf
+git mv lib/version.rb lib/git_tree_version.rb
+git mv test/node/test_node_class.rb test/node_class_test.rb
+git tree
+.
+├── lib
+│   └── version.rb -> git_tree_version.rb (R+)
+└── test
+    └── node
+        └── test_node_class.rb -> test/node_class_test.rb (R+)
+
 # reset repo
 git reset HEAD --hard
 git clean -xdf
@@ -77,21 +91,27 @@ ___
 ## Development
 
 1. Clone this repository
-   * `git clone https://github.com/knugie/git-status-tree.git`
+   * `git clone https://github.com/wteuber/git-status-tree.git`
    * `cd git-status-tree`
 2. Install dependencies
     * `bundle install`
 3. Run tests
-    * `./test/test_git_status_tree`
-    * Tests include RuboCop code style checks
+    * `rake` - Run all tests and RuboCop checks (default)
+    * `rake test` - Run all tests with code coverage only
+    * `rake test:node` - Run Node class tests only
+    * `rake test:nodes_collection` - Run NodesCollection tests only
+    * `rake test:integration` - Run integration tests
+    * `rake test:utilities` - Run utility tests (RuboCop, SimpleCov, Version)
+    * `rake test_no_coverage` - Run tests without code coverage
+    * `rake all` - Run tests and RuboCop checks
     * SimpleCov generates code coverage reports in `coverage/`
-    * Tests will fail if coverage drops
-    * To skip coverage: `COVERAGE=false ./test/test_git_status_tree`
+    * Coverage reports available in HTML and JSON formats
+    * Tests require 100% code coverage
 4. Run RuboCop separately (optional)
     * `bundle exec rubocop`
     * To auto-correct offenses: `bundle exec rubocop -a`
 5. Run git-status-tree from repository
     * `./bin/git-status-tree`
 6. Build and install local gem
    * `gem build git-status-tree.gemspec`
-   * `gem install git-status-tree-3.0.0.gem`
+   * `gem install git-status-tree-3.1.0.gem`

VERSION

@@ -1 +1 @@
-3.0.0
+3.1.0