Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: command 'git add .' #92

Closed
brasilikum opened this issue Sep 1, 2016 · 8 comments
Closed

Bug: command 'git add .' #92

brasilikum opened this issue Sep 1, 2016 · 8 comments

Comments

@brasilikum
Copy link

When I entered 'git add .' in the command field, there was neither a change in the local repo nor did I ever get feedback. The laoding-circle kept loading forever.
'git add content' resulted in the change being made in the local repo, but the output never reached me neither. It kept loading.

@hacdias
Copy link
Member

hacdias commented Sep 1, 2016

Strange... Have you received any error in the Developer Console?

@brasilikum
Copy link
Author

No. Do I have to run caddy other than just 'caddy'?

@hacdias
Copy link
Member

hacdias commented Sep 3, 2016

Hey @brasilikum! On browser, right click in the page and select "Inspect". It will open the Dev Tools. Then open the Console and check if there are any errors there, please :) Like this:

Like this

@brasilikum
Copy link
Author

ok, so this is not so easy to track. It works some times, however as there is no output, I simply thought it had not worked. I will suggest a visual feedback on success in another issue. However the second time I got 403, but also no visual feedback. Why would that be?

@hacdias
Copy link
Member

hacdias commented Sep 7, 2016

Hey Georg! I think that I only return 403 when the error is related to the
permissions. Do caddy has permissions over the files?

Anyway, I will check that out later when I have my laptop. :)

On Wed, 7 Sep 2016, 09:26 Georg Hartmann, notifications@github.com wrote:

ok, so this is not so easy to track. It works some times, however as there
is no output, I simply thought it had not worked. I will suggest a visual
feedback on success in another issue. However the second time I got 403,
but also no visual feedback. Why would that be?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#92 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFMdsNDEtaOymjgckTBYjO95743swJ67ks5qnnVGgaJpZM4JypWk
.

@brasilikum
Copy link
Author

ok, the permissions might be the problem.

@hacdias
Copy link
Member

hacdias commented Sep 7, 2016

Okay, check it out and let me know :)

On Wed, 7 Sep 2016, 09:49 Georg Hartmann, notifications@github.com wrote:

ok, the permissions might be the problem.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#92 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFMdsBd3KkOSZT3P2xrMEsP5AO2GT0ulks5qnnqPgaJpZM4JypWk
.

@hacdias
Copy link
Member

hacdias commented Sep 22, 2016

I'm going to close this due to its inactivity. If there are any updates, tell me!

@hacdias hacdias closed this as completed Sep 22, 2016
hacdias added a commit that referenced this issue Jul 18, 2017
hacdias added a commit that referenced this issue May 11, 2019
Former-commit-id: e8d1875d505a5084ab0fe6e5f85f640d11eecfc9 [formerly 8e2eeecceff1e10f538dfb004553802925d6804d] [formerly f525403b87330bad37325a285cd8d02cfdb691cf [formerly 5b5f799]]
Former-commit-id: eee0030a1d35ac7808854b0bcb8e27805bc8269e [formerly bd4e6f138ebe49b73c3ac72889970301652eb999]
Former-commit-id: 9beb9cbc787c7bf4d590025f438192bfcc0cfc59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants