Skip to content

docs: group all 770 open PRs by algorithm directory in hacktober_2026_prep.md - #15183

Closed
priya-sundaram-dev wants to merge 1 commit into
TheAlgorithms:masterfrom
priya-sundaram-dev:tracker-group-open-prs-by-directory
Closed

docs: group all 770 open PRs by algorithm directory in hacktober_2026_prep.md#15183
priya-sundaram-dev wants to merge 1 commit into
TheAlgorithms:masterfrom
priya-sundaram-dev:tracker-group-open-prs-by-directory

Conversation

@priya-sundaram-dev

Copy link
Copy Markdown
Contributor

As requested by @cclauss on #15081, adds a new section at the bottom of docs/hacktober_2026_prep.md grouping all 770 open pull requests by the algorithm directory they modify, in the requested format:

Total open pull requests: 770

audio_filters:
1. [ ] #14979
backtracking:
1. [ ] #10102
...

How it was built: I examined the changed files of every open PR (GET /pulls/{n}/files) and bucketed each by its top-level algorithm directory. Each PR appears in exactly one grouping (verified: 770 assigned, 0 duplicates).

Special groupings (as you specified):

  • Modifies multiple algorithm directories — 53 PRs touching more than one top-level algorithm dir.
  • Modifies no algorithm directories — 36 PRs touching only non-algorithm paths (.github/, scripts/, docs/, root files).
  • Modifies DIRECTORY.md — 1 PR touching only DIRECTORY.md.

Largest buckets: maths (105), sorts (67), machine_learning (58), data_structures (57), strings (45), searches (33).

The audio_filters group has a single PR (#14979) — happy to start there with Approve / Request changes once scripts/find_git_conflicts.sh (#15181) is sorted.

Docs-only change; nothing under an algorithm directory is touched.

@algorithms-keeper

Copy link
Copy Markdown

Closing this pull request as invalid

@priya-sundaram-dev, this pull request is being closed as none of the checkboxes have been marked. It is important that you go through the checklist and mark the ones relevant to this pull request. Please read the Contributing guidelines.

If you're facing any problem on how to mark a checkbox, please read the following instructions:

  • Read a point one at a time and think if it is relevant to the pull request or not.
  • If it is, then mark it by putting a x between the square bracket like so: [x]

NOTE: Only [x] is supported so if you have put any other letter or symbol between the brackets, that will be marked as invalid. If that is the case then please open a new pull request with the appropriate changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting reviews This PR is ready to be reviewed invalid

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant