Click here for a sample repo (my LeetCode repo)

WikiLeet is a program that takes your local LeetCode submissions and organizes them into a navigatable wiki-like set of markdown files giving you an aesthetically pleasing README to view your journey. See the link above for my own LeetCode repo as an example.

Using GitHub actions, it will run everytime you commit a new submission to your linked repo, updating all the markdown links in the process.

1. In your repo on github.com, click on Actions and ensure that actions are enabled for this repo. Then in your repo create a folder
2. Create a .github/workflows/ folder/directory in your repo.

./project root
└── .github
    └── workflows

3. Create a main.yml file in this folder

./project root
└── .github
    └── workflows
        └── main.yml

4. Paste the following code into the file. Make sure to insert your own LeetCode username!

name: '[Updating markdown files]'

on:
    # Allows for munual runs of workflow
    workflow_dispatch:

    # Default whenever a new code file is pushed to the main branch
    push:
        branches:
            - main
        paths:
            - 'my-submissions/**'

permissions:
    contents: write

jobs:
    build:
        runs-on: ubuntu-latest
        
        steps:
            - name: Call and run markdown generator
              uses: Zanger67/WikiLeet@main
              with:
                # Insert your LeetCode username here!
                username: Zanger

• Categories

  • The NeetCode150 and Blind75 lists have been added.
  • If you put "Daily" or "Weekly Premium" in the file's name, it will categorize them as such.

• Each question

  • Contains a completion date, last attempted date, acceptance rate, related topics, languages used, etc.
  • Each question has a markdown generated containing all solutions (if you have multiple) with all relevant details.
  • If you create a .txt or .md file with a question number (e.g. 1234.py), it will be inserted as a "summary" in the question's markdown. I personally use this to place my notes that I created while working on the problem. Click here for an example.

• Contests

  • In your submissions folder, if you want contests to be group, you can create a folder.
  • Any questions in that folder will be attributed to the contest of the folder's name. Click here for an example.

• Auto-uploading submissions

  • If you use extensions that automatically pulll your submissions, as long as the question's number is present in the file name and it's not in a folder, it will work perfectly.
  • E.g. with the vscode-leetcode extension, you can set the my-submissions as the file store location and the script will parse it all the same.

• Creation and modification dates

  • Default times are set based off of UTC commit times since that's what LeetCode goes off of.
  • These are tracked based off of your commit history by default. The script parses every file associated with a question up it's commit log finding the earliest and latest dates.
  • If ran manually, this can be done using the file creation and modification dates.
  • Warning: parsing the git commit history of each file is slow when done locally it seems but on GitHub actions, it's relatively fast. I'm not sure why this is, but to run locally look at the flag instructions for -n and -g in the main.py file's main().

The program can be ran locally once imported as a submodule via running main.py or main.ipynb.

Click here to see my own repo as an example

• In each new week, you may have a case where it shows a case of +[# of questions solved] lines -[# of questions solved] lines. This is likely the due to the AC rates being updated for the week.
• Occasionally, a lot of lines may be updated on the generalized files (README.md, Mediums.md, Arrays.md, etc.). If the question you add increases the width of a markdown file, it'll update the whole table width to match causing this. For instance, if my Languages column is usually just py, java but then for the first time I have a 3rd language for py, java, js, it'll udpate the column width so it "seems" like a lot of lines.

• Auto detection for Daily and Weekly Premium questions (e.g. commit time +/- 1 day)