How xchux/leetcode-note works
Project type and purpose
• This is an open-source “knowledge-base” repository that organizes and publishes your LeetCode problem solutions in Java and Python. It’s not a running service or web app, but rather a structured collection of code, documentation, and a CI/CD pipeline for quality checks.
File structure
• Top-level:
• .github/workflows/code-check.yml → CI configuration
• README.md → project overview
• pyproject.toml → Python packaging/formatting config (e.g., black, flake8)
• solutions/ → one folder per problem number; each contains a problem-specific README and solution files (.java, .py)
• Notice “solutions/template” as an extensibility point for adding new problems following a consistent structure.
README for additional insights
• Describes the goal (“A Record of My Problem Solving Journey”), update cadence, and references external resources.
• No runtime architecture described, but it implies a CI-driven workflow and static-content publishing on GitHub.
Detail
• Every directory of importance is represented (e.g., highlight .github/workflows, pyproject.toml, solutions/11.…, solutions/template)
• Flow of edits, validations, and publication