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

Create dev.txt #171

Closed
wants to merge 2 commits into from
Closed

Conversation

kaysiz
Copy link

@kaysiz kaysiz commented Oct 20, 2017

Checklist

  • My branch is up-to-date with the upstream develop branch.
  • I have added necessary documentation (if appropriate).

Which issue does this PR fix?: fixes #
#165
Brief description of what this PR does.
added the dev.txt file, empty for now
Add issue number here. If you do not solve the issue entirely, please change the message e.g. "First steps for issues #IssueNumber"
First Steps for Issues #165
Why do we need this PR?:
Other users can update the file
If relevant, please include a screenshot.

Demo (optional):

Some tips for you to write the instructions:

  • Prefer bulleted description
  • Start after checking out this branch
  • Include any setup required, such as migrating databases, etc.

Testing instructions:

If there is any work still left to do, please add it here.

TODOs (if any):

A picture of a cute animal (not mandatory but encouraged):

@coveralls
Copy link

Coverage Status

Coverage remained the same at 67.619% when pulling 4498c77 on kaysiz:patch-1 into 575c764 on OpenSourceHelpCommunity:predev.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 67.619% when pulling 305c686 on kaysiz:patch-1 into 575c764 on OpenSourceHelpCommunity:predev.

@@ -0,0 +1,7 @@
coverage==4.4.1
dj-database-url==0.4.2
Django==1.11.6
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need not repeat this in dev.txt. You can start with -r prod.txt in dev.txt. Have all but coverage in prod.txt. Just have coverage here. Also merge #171 and #172. I will close #172. Then we are good to go with this!

@jarifibrahim
Copy link
Member

@kaysiz Ping!! Are you still working on this?

@kaysiz
Copy link
Author

kaysiz commented Nov 12, 2017

@jarifibrahim ping!! No i am not.

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

Successfully merging this pull request may close these issues.

5 participants