m1guelpf / m1guelpf/auto-commit

auto-commit does not auto-install

Open
#5 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.2k
Forks
61
PR merge metrics
No merged PRs in 30d

Description

m1:auto-commit nv$ curl -fsSL https://raw.githubusercontent.com/m1guelpf/auto-commit/main/install.sh | sh -
https://github.com/m1guelpf/auto-commit/releases/latest/download/auto-commit-darwin-aarch64
downloading latest binary
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 5023k  100 5023k    0     0  1009k      0  0:00:04  0:00:04 --:--:-- 1147k
installed - Auto Commit 0.1.5
m1:auto-commit nv$ auto-commit --help
-bash: auto-commit: command not found
m1:auto-commit nv$

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading install.sh and reproducing the macOS aarch64 installation shown in the issue. Check why the installed auto-commit binary is not available to the shell, then verify that a fresh install allows auto-commit --help to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.