Closed jbrochar closed 7 years ago
Jules, Can you document your change please? Jean.
The relevant change are already commented (see the commit messages). Nevertheless there is probably a mistake somewhere from my side as I don't understand why my "pull" show up here (all the " Merge remote-tracking branch 'upstream/master' " just correspond to me pulling the most recent changes to my local repository) ...
The individual commit messages will disapear when the pull request is validated. In order to avoid polluting the master history with all the details of your progress (in particular all the merges you had to do to keep up with the upstream repo), the whole set of changes contained in your pull request will be appplied to the master as one unique commit (squash merge). The message of this commit will be by default set to the descrition text you provide. So you should edit the description above to summarize the feature provided by your contribution.
Ok I'll do it, thanks.
If you want to avoid the annoying Merge remote-tracking branch 'upstream/master'
, switch on the rebase option when you pull.
I think it would be better if you developed directly in the MBB-team/VBA-toolbox instead of in your fork (you're part of the team, don't be shy!).
Add the MBB-team/VBA-toolbox in your list of remotes:
git remote add mbb-remote git@github.com:MBB-team/VBA-toolbox.git
then
git push mbb-remote master:jbrochar
Is this pull request still on hold? Should I try to squash it in the development branch?
For me it should have been incorporated a while ago.
@jbrochar: could you open the same pull request toward the developement branch? I am a bit reluctant about puting everything in the master...
nevermind, found how to do it
Fix for several small issues about mediation analysis and RFT: