0
good afternoon.
Then someone can help me with a problem in the GIT and HEROKU process.
'-m' is not being recognized when performing the following command.
$ git push -m master
I performed the following commands and the following error appeared:
(venv) gabriel@gabriel-Aspire-F5-573:~/Área de Trabalho/Curso/venv/projetofinal2$ git init
Reinitialized existing Git repository in /home/gabriel/Área de Trabalho/Curso/venv/projetofinal2/.git/
(venv) gabriel@gabriel-Aspire-F5-573:~/Área de Trabalho/Curso/venv/projetofinal2$ git add .
(venv) gabriel@gabriel-Aspire-F5-573:~/Área de Trabalho/Curso/venv/projetofinal2$ git commit -m "first commit"
[master 6aecfe4] first commit
1 file changed, 1 insertion(+), 1 deletion(-)
(venv) gabriel@gabriel-Aspire-F5-573:~/Área de Trabalho/Curso/venv/projetofinal2$ heroku create
Creating app... done, ⬢ arcane-temple-74203
https://arcane-temple-74203.herokuapp.com/ | https://git.heroku.com/arcane-temple-74203.git
(venv) gabriel@gabriel-Aspire-F5-573:~/Área de Trabalho/Curso/venv/projetofinal2$ git push -m master
error: unknown switch `m'
uso: git push [<options>] [<repository> [<refspec>...]]
-v, --verbose be more verbose
-q, --quiet be more quiet
--repo <repository> repository
--all push all refs
--mirror mirror all refs
--delete delete refs
--tags push tags (can't be used with --all or --mirror)
-n, --dry-run dry run
--porcelain machine-readable output
-f, --force force updates
--force-with-lease[=<refname>:<expect>]
require old value of ref to be at this value
--recurse-submodules[=<check|on-demand|no>]
control recursive pushing of submodules
--thin use thin pack
--receive-pack <receive-pack>
receive pack program
--exec <receive-pack>
receive pack program
-u, --set-upstream set upstream for git pull/status
--progress force progress reporting
--prune prune locally removed refs
--no-verify bypass pre-push hook
--follow-tags push missing but relevant tags
--signed[=<yes|no|if-asked>]
GPG sign the push
--atomic request atomic transaction on remote side
(venv) gabriel@gabriel-Aspire-F5-573:~/Área de Trabalho/Curso/venv/projetofinal2$
I also performed the command below:
$ git push --m master
But there was another mistake:
(venv) gabriel@gabriel-Aspire-F5-573:~/Área de Trabalho/Curso/venv/projetofinal2$ git push --m master
fatal: 'master' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Do you just want to push to master? If yes, would be enough:
git push origin master. I don’t understand the-min charge during push, I don’t know what it does.– Dherik
"-m" is to add the commit message, it would look like "git commit -m <my message>", in "git push" (command to send to the central repository) I believe that there is no "-m". But I’m not really familiar with the question of deploying in Heroku, so I can’t say that’s the problem.
– Adriano Gomes
Searching here in the stack, I saw this question, see if it helps you: https://answall.com/questions/75445/up_filevos-ap%C3%B3s-deploy-no-Heroku
– Adriano Gomes