https://github.com/b1f6c1c4/git-fancy-push
The Ultimate Solution towards "shallow update not allowed" in git push
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (7.5%) to scientific vocabulary
Keywords
Repository
The Ultimate Solution towards "shallow update not allowed" in git push
Basic Info
Statistics
- Stars: 3
- Watchers: 1
- Forks: 0
- Open Issues: 1
- Releases: 0
Topics
Metadata Files
README.md
git-fancy-push: "shallow update not allowed" killer
The ULTIMATE solution towards "shallow update not allowed" during a git push
:worried: :frowning: :anguished: Ever seen this is your life? Got annoyed? :anguished: :frowning: :worried:
```bash git push origin master
To github.com:...
! [remote rejected] master -> master (shallow update not allowed)
error: failed to push some refs to 'git@github.com:...
```
:wink: :kissingsmilingeyes: :stuckouttongue: Here is your solution! :stuckouttongue: :kissingsmilingeyes: :wink:
(Guranteed no hidden --unshallow. Instant upload to GitHub.)
```bash
Get jq
(which pacman && sudo pacman -S jq) || (which apt-get && sudo apt-get install jq) || (which brew && brew install jq) which jq
Get git-fancy-push
mkdir -p ~/.local/bin/ && curl -o ~/.local/bin/git-fancy-push https://raw.githubusercontent.com/b1f6c1c4/git-fancy-push/master/git-fancy-push which git-fancy-push || export PATH="$HOME/.local/bin:$PATH"
Do the push
git fancy-push origin master
...
Notice: Push successful! (to ...)
...
```
Usage
The CLI is 100% compatible with that of git push. You just replace git push with git fancy-push.
Of course, you need to put the git-fancy-push script in your PATH some where.
It will start fixing the problem once you encounter a "shallow update not allowed" problem.
If you enounter problem, you can add --verbose as the first argument for git-fancy-push, like this:
git fancy-push --verbose origin master
Dependency
jq- herebashgitcurlawk
Internals
git-fancy-push is based on GitHub v3 API.
It recursively reads the commits that are not yet on GitHub and upload it using GitHub API.
Limitation
- It will only work for GitHub.
Both
git@github.com:orhttps://github.com/will work. It won't work forfile://, GitLab, BitBucket, etc. If you want support for other platforms, create an issue or pull request. - It will fail on commits with a
mergetagheader, which will be added by newer versions of Git during merging a signed annotated tag.
License
MIT
Owner
- Login: b1f6c1c4
- Kind: user
- Location: NJ, USA
- Company: Princeton University
- Repositories: 26
- Profile: https://github.com/b1f6c1c4
52BE D143 A92D BE96 2B83 092B 9BAC 0164 9600 1E70
GitHub Events
Total
Last Year
Issues and Pull Requests
Last synced: 11 months ago
All Time
- Total issues: 1
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 1
- Total pull request authors: 0
- Average comments per issue: 0.0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- b1f6c1c4 (1)