Javier Buzzi comments

Results 148 comments of


                                            Javier Buzzi

'git-crypt status' with the '-f' option to stage an encrypted version fails for me?

@ipatch following your instructions to the letter. Still not working for me. I either get: ``` $ git-crypt status -f Error: a9docs-pybackend/.env.integr: still unencrypted even after staging Unable to stage...

git-crypt unlock not working

@jerger bump.

'status' in fix mode does not successfully fix

Whats the alternative to this?

docker for tutorial

I don’t see a reason for this to be in the project. This should live in a `django-tenant-schemas-docker-demo` repo. My 2 cents.

Optional auto adding namespace the functions used in the code and reverse_code arguments of RunPython

That makes sense, PRs are welcome :D

Optional auto adding namespace the functions used in the code and reverse_code arguments of RunPython

Inside the [extract_function()](https://github.com/kingbuzzman/django-squash/blob/master/django_squash/management/commands/lib/writer.py#L203), it [gets called here](https://github.com/kingbuzzman/django-squash/blob/master/django_squash/management/commands/lib/writer.py#L221-L223). Please add an option to turn function renaming on/off. In case someone wants to opt out. Lastly. Please add tests. I can't stress...

Javier Buzzi

'git-crypt status' with the '-f' option to stage an encrypted version fails for me?

git-crypt unlock not working

'status' in fix mode does not successfully fix

docker for tutorial

Optional auto adding namespace the functions used in the code and reverse_code arguments of RunPython

Optional auto adding namespace the functions used in the code and reverse_code arguments of RunPython

Hello again, sorry I missed your answer. So I plan to reopen issue, cause I tried to squash my migrations again :)

Hello again, sorry I missed your answer. So I plan to reopen issue, cause I tried to squash my migrations again :)

Hello again, sorry I missed your answer. So I plan to reopen issue, cause I tried to squash my migrations again :)

Hello again, sorry I missed your answer. So I plan to reopen issue, cause I tried to squash my migrations again :)