https://github.com/me-on1/leetcode-syncinaction

GitHub Action to Sync your Leetcode Accepted Solution with GitHub repo acts as a personal leetcode archive.
https://github.com/me-on1/leetcode-syncinaction

github-actions leetcode leetcode-cpp leetcode-solutions leetcode-submissions sync

Last synced: 10 days ago
JSON representation

GitHub Action to Sync your Leetcode Accepted Solution with GitHub repo acts as a personal leetcode archive.

• Host: GitHub
• URL: https://github.com/me-on1/leetcode-syncinaction
• Owner: ME-ON1
• License: mit
• Created: 2021-08-20T06:52:09.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2021-11-12T11:04:35.000Z (about 3 years ago)
• Last Synced: 2024-11-17T19:43:34.699Z (about 1 month ago)
• Topics: github-actions, leetcode, leetcode-cpp, leetcode-solutions, leetcode-submissions, sync
• Language: JavaScript
• Homepage:
• Size: 3.99 MB
• Stars: 3
• Watchers: 2
• Forks: 0
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# LC-SyncInAction

Why take the effort of copy/pasting your solution manually when you can make use of technology to do it for you while you can grind more in Leetcode.

LC-SyncInAction solves this problem and takes your cookie in his hand to pull and push your Accepted solution every day.

First run will pull all your Accepted solutions from LC ( which will take **1h 45 min to 2h 30 min approx** ) and create a file with a extension of those submission in the current repository in the specified directory (root, if not provided ). Currently provide extension support for all languages accepted by leetcode 

Every file created using this tool follows this naming convention : _. [SEE THIS EXAMPLE REPO ](https://github.com/ME-ON1/leetcode-bunker/)

All the runs afterward won't take long as the first run ( will be completed in few seconds :) ) and will fetch the last 20 submissions and this step can also be customized according to your preferred timing with the help of [schedule](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#scheduled-events)

### Requirements : 

`cookie` value from the request headers  https://leetcode.com/ 

This cookie value has to be saved in repository secret named as `cookieVal` which **has to be** passed as `${{ secrets.cookieVal }}` into action step [you can look here on how to do save a repository secret](https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)

You can also pass location of directory, to option `solution_location` , where would you like to collect all your solutions ( the default is root directory ). 

## Usage

Make a `WORKFLOW` file under `.github` folder by any name of your choice and start writing github actions. 

Example use case of action in your WORKFLOWS.

    

    on: 

        schedule: 

            - cron : '0 8 * * *' # your favourable timing

    

    jobs : 

      build :

        run-on : ubuntu-latest 

      steps : 

        -name : Using LC-Collectinator

         uses : ME-ON1/Leetcode-SyncInAction

            with :

              cookieVal : ${{ secrets.COOKIE_SECRET }} # secrets.cookieVal coming from repository secret    

              solution_location : path/to/directory  # if any , default is root ./

          

        # dependency, to write newly created files to the root directory of the repository.  

    

        - name: pushing the changes!!

        uses: stefanzweifel/git-auto-commit-action@v4

        with:

          commit_message: Adding new LC solutions # or anything you want to add.

If you need to look at examples check [.github/WORKFLOWS](https://github.com/ME-ON1/Leetcode-SyncInAction/tree/main/.github/WORKFLOWS) to understand a bit more.

## License

The scripts and documentation in this project are released under the [MIT License](https://github.com/ME-ON1/Leetcode-SyncInAction/blob/main/LICENSE)

  

## Issues 

Please file an Issue with brief information about the bug.