-
Notifications
You must be signed in to change notification settings - Fork 56
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
Separate settings file for dev, predev and production #164
Comments
I could work on this if no one took this up already. |
@amakarudze sure!! You can take this issue |
@amakarudze Any updates? |
I have done 2 separate pull requests I am failing to merge to make one. Am
not sure how to do that unfortunately. Am not that experienced with git.
…On Dec 12, 2017 09:18, "Anubha Kushwaha" ***@***.***> wrote:
@amakarudze <https://github.com/amakarudze> Any updates?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AM9qxcfbaCsCNpp_9bzdoarZp3XvTzZ6ks5s_ijcgaJpZM4QAjTw>
.
|
@amakarudze Please let us know your problem and maybe we can help you :) |
@amakarudze The easiest way is to close those pull request and then create new with your changes. |
Alright. Noted with thanks. Let me do so.
…On Dec 15, 2017 16:26, "Tapasweni Pathak" ***@***.***> wrote:
@amakarudze <https://github.com/amakarudze> The easiest way is to close
those pull request and then create new with your changes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AM9qxS87CleSperwTk3YoPLgGMjRzlwyks5tAoGPgaJpZM4QAjTw>
.
|
I have followed Tapasweni's advice and closed the pull requests and created
another one.
Should I worry about hound checks which do not recognize `from base import
*`?
…On 12 December 2017 at 16:56, Anubha Kushwaha ***@***.***> wrote:
@amakarudze <https://github.com/amakarudze> Please let us know your
problem and maybe we can help you :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AM9qxTolUwqgme27NU6sACVl87S6P903ks5s_pQJgaJpZM4QAjTw>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we have one settings file running for all the deployments.
Few important changes required our :
The text was updated successfully, but these errors were encountered: