Modernize GitHub Action to auto-generate DIRECTORY.md

[DenizAltunkapan]

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized it.
• All filenames are in PascalCase.
• All functions and variable names follow Java naming conventions.
• All new algorithms have a URL in their comments that points to Wikipedia or other similar explanations.
• All new code is formatted with clang-format -i --style=file path/to/your/file.java

Refactored the workflow to automatically generate and commit DIRECTORY.md on each push. All classes and tests are now listed in a modern and readable format.

Example:

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.17%. Comparing base (13d8a28) to head (c3645bc).
Report is 7 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #6308      +/-   ##
============================================
+ Coverage     74.14%   74.17%   +0.03%     
- Complexity     5360     5362       +2     
============================================
  Files           678      678              
  Lines         18686    18686              
  Branches       3625     3625              
============================================
+ Hits          13854    13860       +6     
+ Misses         4275     4272       -3     
+ Partials        557      554       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[DenizAltunkapan]

If desired, the generator can be configured to show only Java files in the main directory, excluding tests. Let me know!

[siriak]

Is there an example of diff between old and new DIRECTORY?
Is it possible to include directory tree generator script directly into workflow?

[DenizAltunkapan]

Is there an example of diff between old and new DIRECTORY? Is it possible to include directory tree generator script directly into workflow?

Old Version:

My Version:

yes, technically i think it might be possible to include the directory tree generator script directly into the workflow. However, I’ve chosen to reference it from my own repository to keep things modular and maintainable — plus, it’s more fun that way 🙂

[siriak]

Ok, just please remove .java extension from file names, everyting else looks good

[DenizAltunkapan]

Ok, just please remove .java extension from file names, everyting else looks good

@siriak Okay easy, will do! Just one thing to note: the old version didn’t include the test files, but my version does.
Should I keep showing both main and test files, or should I limit it to just the main files?

[siriak]

The old version does include test files too

[DenizAltunkapan]

Please don't merge yet. I am going to test it again tmrw