{"id":29016245,"url":"https://github.com/otechdo/zazen","last_synced_at":"2025-10-08T03:17:53.095Z","repository":{"id":251190709,"uuid":"836675794","full_name":"otechdo/zazen","owner":"otechdo","description":null,"archived":false,"fork":false,"pushed_at":"2024-08-07T06:35:56.000Z","size":88,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2025-06-14T21:03:31.133Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Rust","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/otechdo.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","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-08-01T10:24:21.000Z","updated_at":"2024-08-07T06:35:59.000Z","dependencies_parsed_at":"2024-08-03T17:22:25.002Z","dependency_job_id":null,"html_url":"https://github.com/otechdo/zazen","commit_stats":null,"previous_names":["otechdo/zazen"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/otechdo/zazen","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/otechdo%2Fzazen","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/otechdo%2Fzazen/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/otechdo%2Fzazen/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/otechdo%2Fzazen/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/otechdo","download_url":"https://codeload.github.com/otechdo/zazen/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/otechdo%2Fzazen/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":261960464,"owners_count":23236575,"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","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":"2025-06-25T22:07:49.166Z","updated_at":"2025-10-08T03:17:48.056Z","avatar_url":"https://github.com/otechdo.png","language":"Rust","funding_links":[],"categories":[],"sub_categories":[],"readme":"---\ntitle: zazen(1)\nsection: 1\ndate: 2024-08-04\nmanual: Zazen Manual\nsource: Zazen Project\n---\n\n# NAME\n\nzazen - offer a better workflow for developer using git and rust\n\n# SYNOPSIS\n\nzazen\n\n# DESCRIPTION\n\nWhat are they?\n\nCommit Message Management: The practice of writing clear, consistent, and informative commit messages to improve project collaboration and understanding.\n\nCosmic Commit Types: A specific convention for commit messages that uses terms and concepts from astronomy and space exploration to categories changes. \n\nThis makes messages more engaging and easier to interpret.\nWhy use commit message management?\n\nEnhanced Collaboration: Clear messages help team members understand the context and purpose of each change.\n\nImproved History Tracking: Well-structured commit logs make it easier to trace the development process, find specific changes, and generate meaningful change logs.\n\nStreamlined Review: Concise and descriptive messages simplify code reviews and help identify potential issues faster.\n\n1. Team Adoption:\n\nDiscuss and Agree: Initiate a conversation with your team about using cosmic commit types. Explain the benefits, share this comprehensive guide, and gather feedback.\nCustomize: Collaboratively decide on the specific commit types you want to use. You can start with the comprehensive list provided here and tailor it to your project's specific needs and preferences.\nDocument: Create a clear and concise reference document outlining the chosen commit types, their meanings, and examples. Make this document easily accessible to all team members.\n\n2. Implementation:\n\nManual Approach: You can start using cosmic commit types manually by simply adhering to the \u003ctype\u003e(\u003cscope\u003e): \u003cshort summary\u003e format in your commit messages.\n\nGit Commit Template: Create a Git commit template file (e.g., .gitmessage) to automatically populate the commit message format in your editor. This can help enforce consistency and remind contributors of the available commit types.\n\nGit Hooks: Utilize Git hooks, like the prepare-commit-msg hook, to validate your commit messages and ensure they conform to the chosen format.\nAutomated Tools: Consider leveraging tools like commitizen or cz-cli that provide interactive prompts for creating commit messages according to your chosen convention. These tools can streamline the process and enforce consistency across your team.\n\n3. Continuous Improvement:\n\nRegular Review: Periodically review your team's commit history to ensure consistent usage of the cosmic commit types and identify any areas where the format could be refined or improved.\n\nFeedback Loop: Encourage open communication and feedback from your team members about the effectiveness of the chosen commit types and any suggestions for improvement.\n\nIterative Refinement: Don't be afraid to experiment and adapt the commit types to better suit your evolving project needs. The key is to find a system that works well for your team and enhances your Git workflow.\n\n4. Continuous Improvement:\n\nEncourage Creativity: While maintaining consistency, allow team members to add their own flair and personality to the commit messages within the established framework.\n\nCelebrate Milestones: Use special event commit types like \"Moon Landing\" to celebrate significant achievements and keep your team motivated.\nIntegration with Other Tools: Explore integration options with your issue tracking system, CI/CD pipeline, or documentation tools to automate processes and maximize the benefits of using cosmic commit types.\n\nBy embracing this comprehensive guide and incorporating cosmic commit types into your Git workflow, you can transform your commit history into a vibrant, informative, and enjoyable reflection of your project's journey.\n\nThe overall goal of Cosmic Commits is to make Git commit messages more informative, engaging, and enjoyable for developers, ultimately leading to better collaboration, maintainability, and understanding of the project's history.\n\nWhy automate commit messages?\n\nWhile Angular Commit Message Conventions provide a clear and structured format, enforcing it manually can be cumbersome and error-prone. Automated commit message generation tools help you:\n\nEnsure Consistency: All commit messages adhere to the convention, making the Git history more organized and easier to analyze.\n\nSave Time: Contributors don't have to manually format messages, leading to a more efficient workflow.\n\nReduce Errors: The tool guides contributors to create valid messages, preventing typos or inconsistencies.\n\nWhy use cosmic commit types specifically?\n\nDescriptive: Terms like \"Star\" (new feature) or \"Comet\" (bug fix) are instantly recognizable and convey the nature of the change at a glance.\n\nEngaging: The cosmic theme adds a fun and memorable element to commit messages.\n\nStandardize: Provides a shared vocabulary and structured format for commit messages, improving consistency across the team.\n\nWhy cosmos commit type ?\n\nCosmic commit types offer a unique and engaging way to categories and describe changes in your Git commit history. Here's why they are beneficial:\n\nEnhanced Clarity and Communication:\n\nDescriptive Labels: Using terms like \"Star\" for new features, \"Comet\" for bug fixes, or \"Nebula\" for refactoring instantly conveys the nature of the change to anyone reading the commit log. This improves communication and understanding within the team.\n\nVisual Scanning: The use of vivid imagery associated with celestial bodies and events makes it easier to quickly scan through a commit history and identify specific types of changes.\n\nContextual Information: The optional addition of a scope within the commit message provides further context about which part of the code base was affected (e.g., \"Star(UI)\" for a new UI feature).\n\nImproved Organization and Maintainability:\n\nStructured Format: The consistent format of cosmic commit messages (e.g., \"Type(Scope): Short summary\") makes the commit history more organized and easier to parse. This helps with tasks like generating change logs or filtering commits based on specific criteria.\n\nStreamlined History: A well-organized commit history makes it easier to track the evolution of the project, identify patterns, and quickly pinpoint the introduction of specific changes.\n\nIncreased Engagement and Fun:\n\nCreative Expression: The cosmic theme adds a touch of personality and fun to the often mundane task of writing commit messages. It can make the development process more enjoyable and engaging for the team.\n\nShared Vocabulary: Using a common set of commit types fosters a sense of shared understanding and camaraderie within the team. It can also serve as a fun conversation starter or icebreaker.\n\nAutomation and Tooling:\n\nChange log Generation: Many tools can automatically generate change logs or release notes by parsing commit messages. Cosmic commit types make this process even easier by providing a clear structure and consistent vocabulary that tools can easily understand.\n\nIssue Tracking Integration: If you reference issue numbers in your commit messages, some tools can automatically link commits to their corresponding issues, streamlining your workflow and keeping your project management tools up-to-date.\n\n# OPTIONS\n\n# EXAMPLES\n\nzazen\n\n# SEE ALSO\n\ngit(1), cargo(1)\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fotechdo%2Fzazen","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fotechdo%2Fzazen","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fotechdo%2Fzazen/lists"}