`repository` input doesn't work
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start by reading the action’s repository input definition and entrypoint.sh around line 147, where the log reports repository: command not found; trace how the input is passed to Git commands. Reproduce with the provided workflow and submodule path. Done when the action recognizes the selected repository and completes the commit step without the reported error.
Written by the indexing model from the issue text.
Description
git-auto-commit Version
v3
Machine Type
Ubuntu (eg. ubuntu-latest)
Bug description
Hi!
I have the repostiry with a submodule. This is modified in a process. I want to commit to the submodule repository.
To do this I've tried to set repository: input but it did nothing.
Steps to reproduce
- run my workflow
- will see the crash
Tried solutions
- setting submodule path
- copying submodule to the parent directory (
..) - searching for another action (this one is the best although 😄 )
Example Workflow
on:
workflow_dispatch:
schedule:
- cron: 0 0 * * *
timezone: 'Europe/Warsaw'
jobs:
update-posts:
name: Download posts and push if needed
runs-on: ubuntu-latest
steps:
- name: Check out code
uses: actions/checkout@v7
with:
token: ${{ secrets.FB_WORKFLOW_TOKEN }}
submodules: recursive
- name: Download new posts
run: |
ACCESS_TOKEN=${{ secrets.PAGE_TOKEN }} python scripts/download_posts.py
- name: Dirty hack
run: mv content/posts ../
- run: stat ../posts/.git
- name: Commit changes if needed.
uses: stefanzweifel/git-auto-commit-action@v7
with:
commit_message: Update FB Posts
repository: "../posts/"
Relevant log output
Run stat ../posts/.git
File: ../posts/.git
Size: 41 Blocks: 8 IO Block: 4096 regular file
Device: 8,1 Inode: 8936335 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1001/ runner) Gid: ( 1001/ runner)
Access: 2026-10-20 14:12:03.351338836 +0000
Modify: 2026-10-20 14:12:03.350692592 +0000
Change: 2026-10-20 14:12:03.350692592 +0000
Birth: 2026-10-20 14:12:02.463559265 +0000
0s
Run stefanzweifel/git-auto-commit-action@v7
Started: bash /home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v7/entrypoint.sh
INPUT_REPOSITORY value: ../posts/
/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v7/entrypoint.sh: line 147: repository: command not found
Error: Not a git repository. Please make sure to run this action in a git repository. Adjust the input if necessary.
Error: Invalid status code: 1
at ChildProcess.<anonymous> (/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v7/index.js:17:19)
at ChildProcess.emit (node:events:509:28)
at maybeClose (node:internal/child_process:1141:16)
at ChildProcess._handle.onexit (node:internal/child_process:306:5) {
code: 1
}
Error: Invalid status code: 1
at ChildProcess.<anonymous> (/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v7/index.js:17:19)
at ChildProcess.emit (node:events:509:28)
at maybeClose (node:internal/child_process:1141:16)
at ChildProcess._handle.onexit (node:internal/child_process:306:5)
Repository
No response
- Dominant language
- Shell
- Stars
- 2.6k
- Forks
- 284
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stefanzweifel/git-auto-commit-action
-
"nothing to commit, working tree clean Error: Invalid status code: 1" despite `skip_dirty_check`Openbug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
stefanzweifel/git-auto-commit-action#396 · 4 comments ·
All issues in stefanzweifel/git-auto-commit-action
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cov-lineages/pangolin#583 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
obra/superpowers#2567 ·
Maintainers usually reply within 2 days