Skip to content
/ code Public

πŸš€ A LeetCode a day, keep rejection away | Code with Hugo 🫑

License

Notifications You must be signed in to change notification settings

1chooo/code

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

I Code for NO Code. πŸš€

1chooo.com Home Page

The Source Code of my Problem-Solving.

✨ I moved my focus on GO.
Visit my Blog πŸ‘‰πŸ» Hugo's Blog and Medium πŸ‘‰πŸ» Hugo ChunHo Lin.

This repository contains the source code of my problem-solving journey. I will be sharing the process of my problem-solving skills, coding practices, and the journey of my software engineering. I will keep updating this repository with my software engineering journey.

πŸ“‡ My LeetCode Stats

πŸ’ͺ🏻 How to Contribute

Pull requests (PRs) are welcome! πŸŽ‰

Important

Please follow these guidelines to contribute to this repository:

Contributing Guidelines:

  1. If the question or solution already exists, you can edit it directly under the current solution.
  2. If it's a new question or solution, create a new folder with the format: <source>/<id>-<question-name>/solution.<language>
  3. Each commit should address only one question.

File Naming Convention:

  • Use the format: <source>/<id>-<question-name>/solution.<language>
  • For example: leetcode/0001-two-sum/solution.go

Commit Message Format:

  • Use the format: git commit -m "feat(<source>): <id> <question-name>"
  • For example: git commit -m "feat(leetcode): 0001 Two Sum"

Note

Comment Block (Optional):

You can add a comment block at the top of your solution for additional details, such as problem reference, runtime, and author information.

For example:

/**
 * Author: 1chooo<hugo970217@gmail.com>
 * Problem: https://leetcode.com/problems/minimum-string-length-after-removing-substrings
 * Runtime: 3ms (89.08%)
 */

Forking this Repository:

Fork the 1chooo/code repository into your own workspace.

Cloning the Repository to Your Workspace:

$ git clone git@github.com:<your_workspace_name>/code.git

Setting Upstream Remote:

$ git remote add upstream git@github.com:1chooo/code.git

$ git remote -v
origin  git@github.com:<your_user_name>/code.git (fetch)
origin  git@github.com:<your_user_name>/code.git (push)
upstream        git@github.com:1chooo/code.git (fetch)
upstream        git@github.com:1chooo/code.git (push)

Pull Requests:

If you have any valuable ideas to contribute, please create a pull request and provide details about the outstanding work you've done.

Issue Reporting:

If you encounter any problems while contributing to this project, please report the issues in the 1chooo/code/issues section.

Important

Make sure to synchronize and update your repository before writing any code.

  1. Run git stash save to temporarily stash your local changes.
  2. Run git fetch upstream to sync the source project with your local copy.
  3. Run git checkout main to switch to the main branch.
  4. Run git merge upstream/main to merge the updated remote version into your local copy. If there are no conflicts, the update process is complete.
  5. Run git stash pop to apply your temporarily stashed changes back to your working directory. Resolve any conflicts if necessary.

πŸ“± CONTACT INFO.

Hugo ChunHo Lin

πŸ“© E-mail: hugo970217@gmail.com
🧳 Linkedin: Hugo ChunHo Lin
πŸ‘¨πŸ»β€πŸ’» GitHub: 1chooo

πŸͺͺ LICENSE

Released under MIT by @1chooo

This software can be modified and reused without restriction. The original license must be included with any copies of this software. If a significant portion of the source code is used, please provide a link back to this repository.

Made with ❀️ by @1chooo