-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* housekeeping - spell check - consistently use markdown syntax in roxygen docs - style - vignette chunk label fixes - minor rephrasing - update roxygen version - remove unnecessary pander from suggests - follow best practices for Rproject * edits to plot config vignette and sundry * edits to theme maker vignette * edits to the TLF workflow vignette * better chunk options * fix warnings from ggplot2 3.3.3 * revert ggplot2 version bump; spelling * edits to box plot vignette * edits to atom plots vignette * edits to PK ratio vignette
- Loading branch information
1 parent
f6044eb
commit dbaa7a6
Showing
64 changed files
with
1,472 additions
and
1,217 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
dbaa7a6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msevestre Out of curiosity, why does this show up as a single commit in the commit history, when the PR had multiple commits?
dbaa7a6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we had followed the git worklow, we would have had the following
1 - one issue (for instance Housekeeping)
2- on branch fixing this issue
3- you can commit as many times as you want to the branch in #2. But the actual history of how you got there is in most cases irrelevant. For example, one could argue that bump ggplot, undo bump ggplot etc... are not needed in the history
4- We squash and merge those commits into one (only when we merge onto develop)./ That way the history on develop in linear and each commit corresponds to an issue being fixed or a feature being implemented
see https://github.com/Open-Systems-Pharmacology/Suite/blob/develop/GIT_WORKFLOW.md
dbaa7a6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the detailed reply! Makes sense.
Hadn't read the git workflow document, so thanks for sending it along.
dbaa7a6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@IndrajeetPatil We might well decide to revise the flow in the future. (specifically all about the rebase stuff etc... is not easy for everyone and can lead to some massive frustrations...)
Do you see any drawback from "squash and merge" ?
dbaa7a6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, not really. I actually like this cleaner approach!