{"id":21382057,"url":"https://github.com/catmeowbyte/heretic_git_guidelines","last_synced_at":"2026-02-21T14:02:10.190Z","repository":{"id":240936253,"uuid":"803804333","full_name":"CatMeowByte/heretic_git_guidelines","owner":"CatMeowByte","description":"Heretic Git Guidelines (HGG) is a nonconformist Git management guide focusing on flexibility and simplicity for a rapid workflow.","archived":false,"fork":false,"pushed_at":"2024-05-21T13:38:19.000Z","size":1,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-03-16T11:11:21.747Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://catmeowbyte.github.io/heretic_git_guidelines/","language":null,"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/CatMeowByte.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}},"created_at":"2024-05-21T12:18:02.000Z","updated_at":"2024-12-29T08:02:49.000Z","dependencies_parsed_at":"2024-05-21T14:45:55.430Z","dependency_job_id":"a31c3a9f-e81f-40d4-a144-3354fef0b20b","html_url":"https://github.com/CatMeowByte/heretic_git_guidelines","commit_stats":null,"previous_names":["catmeowbyte/heretic_git_guidelines"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/CatMeowByte/heretic_git_guidelines","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/CatMeowByte%2Fheretic_git_guidelines","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/CatMeowByte%2Fheretic_git_guidelines/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/CatMeowByte%2Fheretic_git_guidelines/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/CatMeowByte%2Fheretic_git_guidelines/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/CatMeowByte","download_url":"https://codeload.github.com/CatMeowByte/heretic_git_guidelines/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/CatMeowByte%2Fheretic_git_guidelines/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":279017790,"owners_count":26086143,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-10-14T02:00:06.444Z","response_time":60,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"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":[],"created_at":"2024-11-22T10:51:56.155Z","updated_at":"2025-10-14T03:20:13.124Z","avatar_url":"https://github.com/CatMeowByte.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Heretic Git Guidelines\n\nHeretic Git Guidelines (HGG) is a nonconformist Git management guide focusing on flexibility and simplicity for a rapid workflow.\n\n---\n\n## Purpose\n\nUnlike typical Git guidelines that emphasize best practices with strict rules, this guideline prioritizes flexibility to simplify Git usage, allowing the user to focus more on the project.\n\n#### What It Means\n\nWhile other best practice guides are designed for public repositories with strict rules, HGG mainly focuses on using Git loosely to store projects in a snapshot manner.\n\nFor example, imagine you've made a stack of commits, but then you notice a single-word typo several commits ago. Fixing it requires either writing a long commit title filled with one-character diffs or rebasing the last few commits to amend your fix. Both options are equally messy.\n\nOr, when the project is barely finished and you've built a lot of things from the ground up, using micro commits can easily clutter the history. Sometimes, all you need is just a saved checkpoint snapshot of your work.\n\n---\n\n## Guidelines\n\n+ ### Main\n\n\tTrust the latest HEAD on the main branch as the most updated stable code. Focus on the current state of the codebase and ignore the commit history.\n\n+ ### Branch\n\n\tBranches can be used for experimental or versioning reasons. They provide a sandbox for trying out new features or maintaining different versions of the codebase.\n\n+ ### Commit\n\n\tCommit messages can be simple or detailed, but the primary goal is to capture the state of the project at a given moment. Clarity helps but not mandatory.\n\n+ ### Tags\n\n\tTags are used to mark points of interest in the snapshot history. They are reorderable and sorted by time. Tags can mark when a feature started to work, indicate a to-be-deleted algorithm, highlight other significant events in the project's timeline, etc.\n\n---\n\n## Usage\n\nMention in the project that it uses Heretic Git Guidelines.\n\n---\n\nThis project is licensed under [WTFPL](http://wtfpl.net \"Do What the Fuck You Want to Public License\").\n\nThis project follows the [HGG](https://catmeowbyte.github.io/heretic_git_guidelines \"Heretic Git Guidelines\").\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcatmeowbyte%2Fheretic_git_guidelines","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcatmeowbyte%2Fheretic_git_guidelines","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcatmeowbyte%2Fheretic_git_guidelines/lists"}