"Error: Error: Could not read from remote repository." with @v9
See original GitHub issueDescribe the bug “Error: Error: Could not read from remote repository” error using @v9
The same flow works with v7.5.0
Note: with checkout@v3 I’m using PAT instead of default token.
Similar to https://github.com/EndBug/add-and-commit/issues/199 Workflow used
- name: Update plugins
uses: EndBug/add-and-commit@v9
with:
add: 'my_path'
message: 'CI: Updating control-*.aar [skip ci]'
pull: 'NO-PULL'
Expected behavior git add / git commit / git push
Logs Either provide a link to the action run or (if your repo is private) paste here the logs from the step that uses it. If you paste the logs, please use this template, and remember to paste the logs from all the different sections.
Logs
Run EndBug/add-and-commit@v9
with:
add: my-peth
message: CI: Updating control*.aar [skip ci]
pull: NO-PULL
cwd: .
default_author: github_actor
fetch: --tags --force
pathspec_error_handling: ignore
push: true
github_token: ***
env:
JAVA_HOME: /opt/hostedtoolcache/Java_Zulu_jdk/8.0.35[2](https://github.com/multinarity/SpaceTop-Unity/actions/runs/3361537012/jobs/5572055054#step:12:2)-8/x64
JAVA_HOME_8_X64: /opt/hostedtoolcache/Java_Zulu_jdk/8.0.[3](https://github.com/multinarity/SpaceTop-Unity/actions/runs/3361537012/jobs/5572055054#step:12:3)52-8/x6[4](https://github.com/multinarity/SpaceTop-Unity/actions/runs/3361537012/jobs/5572055054#step:12:4)
Running in /home/runner/work/my-repo/my-repo
Add input parsed as single string, running 1 git add command.
> Using 'vitalyk<vitalyk@users.noreply.github.com>' as author.
> Using "CI: Updating control-*.aar [skip ci]" as commit message.
Internal logs
> Staging files...
> Adding files...
> No files to remove.
> Checking for uncommitted changes in the git working tree...
> Found 2 changed files.
> Fetching repo...
{ raw: '', remote: null, branches: [], tags: [] }
> Pulling from remote...
{ raw: '', remote: null, branches: [], tags: [] }
Error: Error: Could not read from remote repository.
Outputs
committed: false
commit_long_sha: undefined
commit_sha: undefined
pushed: false
tagged: false
tag_pushed: false
Error: Error: Could not read from remote repository.
Issue Analytics
- State:
- Created a year ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
git: fatal: Could not read from remote repository - Stack Overflow
This error means that you have not specified your remote URL location upon which your code will push. You can set remote URL...
Read more >Permission denied (publickey). fatal: Could not read ... - GitHub
Fresh new installation - added a local git repo and then added a new app. Found that it's weird that the branch list...
Read more >Git fatal: Could not read from remote repository Solution
The Git “fatal: Could not read from remote repository” error occurs when there is an issue authenticating with a Git repository. This is...
Read more >How to Get Started with GIT and work with GIT Remote Repo
When a new file is added, it is staged (or indexed, or cached) in the staging area (as shown in the GIT storage...
Read more >Fatal: could not read from remote repository \\ GitHub Error ...
Learn Python For DevOps: https://bit.ly/3JPaT3eWe generally get GitHub ERROR saying please make sure you have the correct access rights or ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Don’t worry ahahaha It can work because the history is not reset when the action runs. As long as you don’t push anything right after the first commit, the second will always be a fast-forward push. This is the same behavior as if you were to use:
NO-PULL
was an option in the past, but it has been removed in v8.0.0 Happy to hear that everything works! I’ll close the issue for now