Use it for Jekyll deploy
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Shell
- Stars
- 5.6k
- Forks
- 694
- PR merge metrics
- No merged PRs in 30d
Description
I try ro use it for Jekyll deploy,but an error happened.
$ git ftp init
fatal: bad default revision 'HEAD'
There are no files to sync.
Last deployment changed from to .
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing git ftp init in the reported Jekyll deployment context and trace how the command handles the default HEAD revision. Confirm the cause of the “bad default revision” error and verify that initialization completes with files available for synchronization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100