Closed awalter-bnl closed 5 years ago
The force push was done to resolve a git commit issue (2 almost identical commits ended up in the history, I squashed them together and then force pushed the result)
Ups, GitHub's "Resolve conflicts" interface produced a merge commit. Will resolve it tomorrow morning.
source/deployment/resyncing-conda.rst
<- that whole file in now wrong, @licode how do we do it now?
Sorry I screwed up the history of the PR after force pushes last night. Now there is a merge-commit 49122949a7001832618495f805a03fa710b1f0fb, which could have been avoided if git pull
was used before committing your changes. @danielballan, what's the best way to remove it?
@mrakitin I did do a git pull
prior to sending in the commit this morning, that is what added merge-commit 4912294. I can squash the last two together to resolve that, I will do so now.
OK so git rebase won't let me squash the merge commit, sorry.
No worries, thanks for trying.
source/deployment/resyncing-conda.rst file is out of date. I can send pr to work on it. Do I send a new one after this get merged? Or I just push to the current pr? It looks like there were some issue, but just got resolved here.
@licode please just push to this one, that way we keep everything together.
thanks for suggestion!
Done.
This PR is a result of a review of the deployment docs section. It involves adding a warning based on an issue from the last cycle, a few grammar re-arrangments and correction of a few typos. I also updated the name of the local anaconda server to alexandria.