{"id":37101887,"url":"https://github.com/angelicagardner/coding-challenges","last_synced_at":"2026-01-14T12:21:40.975Z","repository":{"id":107124658,"uuid":"470915606","full_name":"angelicagardner/coding-challenges","owner":"angelicagardner","description":"Collection of solutions (in Golang) to various coding challenges.","archived":false,"fork":false,"pushed_at":"2025-07-23T18:42:04.000Z","size":72,"stargazers_count":1,"open_issues_count":8,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-07-23T21:26:16.734Z","etag":null,"topics":["coding-challenges","cracking-the-coding-interview","golang","leetcode","project-euler"],"latest_commit_sha":null,"homepage":"","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/angelicagardner.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2022-03-17T08:53:52.000Z","updated_at":"2025-07-23T18:40:31.000Z","dependencies_parsed_at":"2023-08-20T16:46:32.085Z","dependency_job_id":"b311443d-8b0a-4caf-9712-264afe708ab8","html_url":"https://github.com/angelicagardner/coding-challenges","commit_stats":null,"previous_names":["angelicagardner/coding-challenges"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/angelicagardner/coding-challenges","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angelicagardner%2Fcoding-challenges","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angelicagardner%2Fcoding-challenges/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angelicagardner%2Fcoding-challenges/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angelicagardner%2Fcoding-challenges/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/angelicagardner","download_url":"https://codeload.github.com/angelicagardner/coding-challenges/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/angelicagardner%2Fcoding-challenges/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28420547,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-14T10:47:48.104Z","status":"ssl_error","status_checked_at":"2026-01-14T10:46:19.031Z","response_time":107,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["coding-challenges","cracking-the-coding-interview","golang","leetcode","project-euler"],"created_at":"2026-01-14T12:21:40.410Z","updated_at":"2026-01-14T12:21:40.963Z","avatar_url":"https://github.com/angelicagardner.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Coding Challenges\n\nThis repository saves my solutions to the following different coding challenges:\n\n- [Cracking The Coding Interview (CTCI)](https://github.com/careercup/CtCI-6th-Edition)\n- [Interviewing.io](https://interviewing.io/)\n- [Leetcode](https://leetcode.com/)\n- [Project Euler](https://projecteuler.net/archives)\n\nThe solutions are written in Golang.\n\n## Format\n\n1. Problem from one coding challenge is created as an Issue. The issue has relevant Labels and a description of the problem.\n\n2. Solution to a Issue (coding problem) is submitted as a Pull Request. The solution also has an associated _test file with test cases to verify the solution.\n\n3. The solution file will be named to reflect problem name, e.g. **problem_001.go**, and associated test file will have the same name and end with **_test** suffix, e.g. **problem_001_test.go**.\n\n4. The solution file should contain a brute force solution and an improved solution. Write the time and space complexities as comments about the function. The test cases should test both solutions.\n\n### Solution Template\n\n```go\n/*\n[Issue title]\n*/\n\npackage challenge\n\n// Time complexity:     O(n^2)\n// Space complexity:    O(1)\nfunc BruteForceSolution() {\n    // Implementation here\n    return answer\n}\n\n// Time complexity:     O(n)\n// Space complexity:    O(n)\nfunc ImprovedSolution() {\n    // Implementation here\n    return answer\n}\n```\n\n## Set up\n\nThe repository is organised into folders for the different challenges (projects) and each Issue created will belong to one of the challenges, i.e. One Issue = One Problem.\n\nOnce a coding solution is verified, it is merged and placed in the relevant folder - together with the associated test file. The test cases are run in a GitHub Action and the workflow is triggered when a pull request is opened or updated.\n\n### Use Conventional Commits\n\nThis repo automatically lints commit messages with [commitlint](https://commitlint.js.org/) when new pull requests are created and merged to the main branch. To make sure the commit messages are correct, this can be set up locally.\n\n1. Clone the repository\n\n```bash\ngit clone https://github.com/angelicagardner/coding-challenges.git\ncd coding-challenges\n```\n\n2. Make sure you have Node.js and npm installed\n\nIn our GitHub Action we're using Node.js v20.14.0.\n\n3. Husky is used to manage Git hooks\n\nMake sure husky is installed and set it up:\n\n```bash\nnpx husky init\n```\n\n4. Configure Husky Hooks\n\nRemove the \"npm test\" line from .husky/pre-commit file, and add the following line to the file .husky/commit-msg:\n\n\u003e npm run commitlint ${1}\n\n5. Verify\n\nYou can check the last commit and this will return an error if invalid or a positive output if valid:\n\n```bash\nnpx commitlint --from HEAD~1 --to HEAD --verbose\n```\n\nIf everything is set up correctly you will be able to \"git commit\" with a commit message according to the Conventional Commits specification. Read more here: [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fangelicagardner%2Fcoding-challenges","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fangelicagardner%2Fcoding-challenges","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fangelicagardner%2Fcoding-challenges/lists"}