@nozich/git-mood 0.1.2 → 0.1.3

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,26 @@
+---
+name: 🐛 Bug Report
+about: Create a report to help us improve.
+title: 'bug: '
+labels: 'bug'
+assignees: ''
+---
+
+## Description
+Provide a clear and concise description of the bug.
+
+## Steps to Reproduce
+1. Go to '...'
+2. Run command '...'
+3. See error '...'
+
+## Expected Behavior
+Provide a clear description of what you expected to happen.
+
+## Environment Specs
+- **OS**: [e.g. Windows 11, Ubuntu 24.04, macOS Sonoma]
+- **Tool Version**: [e.g. 0.1.2]
+- **Node / Cargo Version**: [e.g. Node 24, Cargo 1.78]
+
+## Additional Context
+Add any other context, logs, or screenshots about the problem here.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: 🚀 Feature Request
+about: Suggest an idea or enhancement for this project.
+title: 'feat: '
+labels: 'enhancement'
+assignees: ''
+---
+
+## Is your feature request related to a problem?
+Provide a clear description of what the problem is (e.g. "I'm always frustrated when...").
+
+## Proposed Solution
+Provide a clear description of what you want to happen and the proposed implementation.
+
+## Alternative Solutions Considered
+Describe any alternative solutions or features you've considered.
+
+## Additional Context
+Add any other context or mockups about the feature request here.

package/.github/pull_request_template.md

@@ -0,0 +1,12 @@
+## Description
+Provide a clear description of the changes introduced by this Pull Request.
+
+## Related Issues
+Fixes # (issue number)
+
+## Checklist
+- [ ] My commits are GPG/SSH signed.
+- [ ] My commit messages follow the Conventional Commits specification.
+- [ ] I have added tests to verify my changes.
+- [ ] All new and existing tests passed.
+- [ ] I have updated the documentation accordingly.

package/CONTRIBUTING.md

@@ -0,0 +1,43 @@
+# Contributing to Nozich Open Source Projects
+
+Thank you for your interest in contributing! To maintain enterprise-grade software standards, we follow a structured contribution flow.
+
+## 1. Branching Strategy & Development Workflow
+
+We follow a strict git branching strategy:
+- **`main` / `master`**: Stable release branch. Direct pushes are disabled/protected.
+- **`feat/*`**: For new features and enhancements.
+- **`fix/*`**: For bug fixes.
+- **`refactor/*`**: For code refactoring or cleaning.
+- **`docs/*`**: For documentation changes.
+
+### Workflow:
+1. Fork the repository.
+2. Create a feature branch from `main` (e.g., `feat/add-json-parser`).
+3. Write clean, modular, and documented code.
+4. Add unit and integration tests to verify your changes.
+5. Verify linting and formatting locally.
+6. Commit your changes (must be GPG/SSH signed).
+7. Push to your fork and submit a Pull Request.
+
+## 2. Commit Message Guidelines
+
+We enforce **Conventional Commits**:
+- Format: `<type>(<scope>): <description>`
+- Examples:
+  - `feat(gateway): add multi-tenant routing rule matcher`
+  - `fix(cli): resolve command-line parser crash on null value`
+  - `docs(readme): update installation binary links`
+
+## 3. Commit Verification (GPG/SSH Signing)
+
+To verify contributor identity, **all commits must be signed**. Ensure your git client is configured with a valid signing key:
+```bash
+git config --global commit.gpgsign true
+```
+Unsigned pull requests will fail validation checks.
+
+## 4. Coding Standards
+
+- **Rust**: Format code using `cargo fmt` and ensure no warnings are returned by `cargo clippy`.
+- **TypeScript / Node**: Follow standard ESLint rules and compile with strict type checking.

package/Cargo.lock

@@ -101,7 +101,7 @@ dependencies = [
 
 [[package]]
 name = "git-mood"
-version = "0.1.0"
+version = "0.1.3"
 dependencies = [
  "chrono",
  "colored",

package/Cargo.toml

@@ -1,7 +1,10 @@
 [package]
 name = "git-mood"
-version = "0.1.2"
+version = "0.1.3"
 edition = "2021"
+description = "Color your GitHub contribution graph with the mood of your git commits"
+license = "MIT"
+repository = "https://github.com/anilcan-kara/git-mood"
 
 [dependencies]
 serde = { version = "1.0", features = ["derive"] }

package/SECURITY.md

@@ -0,0 +1,26 @@
+# Security Policy
+
+We take security vulnerabilities seriously. Thank you for helping keep our open-source tools secure.
+
+## Supported Versions
+
+Only the latest released version of this package is actively supported and receiving security updates.
+
+| Version | Supported |
+| ------- | --------- |
+| Latest  | ✅ Yes    |
+| Older   | ❌ No     |
+
+## Reporting a Vulnerability
+
+**Please do not report security vulnerabilities via public GitHub issues.**
+
+Instead, please send a detailed report to **anilcankara.com@gmail.com**.
+
+Include the following information in your report:
+- Package name and version.
+- Vulnerability type (e.g. buffer overflow, remote code execution).
+- Steps to reproduce or a working Proof of Concept (PoC).
+- Potential impact.
+
+We will acknowledge receipt of your report within 48 hours and coordinate a fix and advisory release.

package/bin/cli.js

@@ -5,7 +5,7 @@ const path = require('path');
 const https = require('https');
 const { spawn } = require('child_process');
 
-const VERSION = '0.1.2';
+const VERSION = '0.1.3';
 const REPO = 'anilcan-kara/git-mood';
 
 const platform = process.platform;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nozich/git-mood",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Color your GitHub contribution graph with the mood of your git commits",
   "main": "bin/cli.js",
   "bin": {

package/src/main.rs

@@ -65,7 +65,7 @@ fn print_help() {
     println!("Usage:");
     println!("  git-mood init           Install git hook in the current repository");
     println!("  git-mood status         Display terminal dashboard of your moods");
-    println!("  git-mood sync           Generate git-mood.svg and push it to profile");
+    println!("  git-mood sync [file]    Generate SVG (defaults to git-mood.svg) and push it");
     println!();
     println!("Hook Command (Internal):");
     println!("  git-mood commit-hook <file>  Analyze commit message file");
@@ -202,12 +202,17 @@ fn main() {
             println!();
         }
         "sync" => {
-            println!("{} Generating git-mood.svg...", "[git-mood]".green());
+            let svg_filename = if args.len() >= 3 {
+                &args[2]
+            } else {
+                "git-mood.svg"
+            };
+            println!("{} Generating {}...", "[git-mood]".green(), svg_filename);
             let db_path = get_log_path();
             let db = load_db(&db_path);
 
             let svg_content = svg::generate_svg(&db);
-            let svg_path = Path::new("git-mood.svg");
+            let svg_path = Path::new(svg_filename);
 
             if let Err(e) = fs::write(svg_path, svg_content) {
                 eprintln!("{}: Failed to write SVG file: {}", "Error".red().bold(), e);
@@ -221,7 +226,7 @@ fn main() {
                 
                 // git add
                 let add_status = Command::new("git")
-                    .args(["add", "git-mood.svg"])
+                    .args(["add", svg_filename])
                     .status();
 
                 if let Ok(status) = add_status {