Closed jrleeman closed 8 years ago
I'd use rebase to squash these together once you have it working.
Any idea on why the docs build, but without the proper content? A local build works fine…
On Oct 29, 2015, at 10:44 AM, Ryan May notifications@github.com wrote:
I'd use rebase to squash these together once you have it working.
— Reply to this email directly or view it on GitHub https://github.com/jrleeman/rsfmodel/pull/41#issuecomment-152201765.
Any of those solve it?
Yep. Just adding missing docstrings now. Finally chased all the conspiring factors down.
On Nov 2, 2015, at 2:32 PM, Ryan May notifications@github.com wrote:
Any of those solve it?
— Reply to this email directly or view it on GitHub https://github.com/jrleeman/rsfmodel/pull/41#issuecomment-153133545.
OK, I think this is ready to go. Just rebase master? Anything you see you change?
Just a few inline comments. Squash down the commits if you like, just to capture the individual steps you want in the history. Otherwise, good to go!
Ok. I made another branch to play with squashing down the commits, but didn't get it to work right. What's the right procedure to squash them without replaying them directly on master?
I usually use:
git rebase -i master [yourbranchhere]
Ok. Also, Tavis is dying, but I think it's on the conda/travis side?
The command "conda update --yes conda" failed and exited with 127 during .
Looks like conda install for python 2 changed. See:
PREFIX=/home/travis/miniconda2
and
$ export PATH=/home/travis/miniconda/bin:$PATH
1) I'll have to force the push of my rebase right?
2) So what's the best approach for the travis,yml? We'll have to set something for python 2 and 3 right?
1) Yes, push --force
. Might want to do a --dry-run
(?) to double check what branches are being pushed.
2) When installing miniconda, specify where to install it, $HOME/miniconda
maybe. The commandline flag escapes me right now.
Woohoo! Think we can merge this thing?
Depends...do you like that last commit message? Otherwise, yes.
Won't the squashed commit messages come along too? Sorry, still figuring out how to keep a clean-ish log
When you rebase squash, you can edit the commit message to contain what you want. You can also use fixup and squash a commit and throw away its message.
Ryan
On Nov 4, 2015, at 18:38, John Leeman notifications@github.com wrote:
Won't the squashed commit messages come along too? Sorry, still figuring out how to keep a clean-ish log
— Reply to this email directly or view it on GitHub.
I didn't even notice it had actually inserted my $HOME variable. Anyway, message edited. Merge away if you're happy as well.
I had to add a requirements file to get numpydoc to install for readthedocs to build. Things build now, but still have some issue because the page generated doesn't have anything from the docstrings. http://rsfmodel.readthedocs.org/en/fixdocs/