-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update few files #92
Update few files #92
Conversation
✅ Deploy Preview for playful-gelato-7892ba ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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 PR. I have asked to revert a couple of changes because I believe they were correct.
Regarding your questions:
- Could you submit a PR to add a link to the contributions chapter in
Lines 35 to 40 in bf64c4f
::: {.callout-tip title="Read more about this principle in application"} - [What should the first 100 lines of code written during an epidemic look like?](https://epiverse-trace.github.io/posts/100days-workshop/) - [Communicating development stages of open-source software](https://epiverse-trace.github.io/posts/comm-software-devel/) ::: - I believe what we meant is that co-creation with domain experts can be done via pair programming. Please suggest a better phrasing if it's unclear
- We don't have cheatsheets at the moment as far as I know but here are examples outside of Epiverse: https://rstudio.github.io/cheatsheets/contributed-cheatsheets.html
Co-authored-by: Hugo Gruson <10783929+Bisaloo@users.noreply.github.com>
Co-authored-by: Hugo Gruson <10783929+Bisaloo@users.noreply.github.com>
Co-authored-by: Hugo Gruson <10783929+Bisaloo@users.noreply.github.com>
can't it be done on this PR? given that I have reverted some changes to what was there before as you suggested.
I agree with
thanks for sharing this. Maybe consider adding this as an example:
|
Yes, please feel free to add these 3 changes in this PR. |
If you would like to add any further changes please provide a new PR. I will now merge this as it's been open for over a month without updates, plus the included changes are very minor. I approved the PR to document my approval of the current state. |
In this PR, I have fixed few typos and raised few questions/suggestions:
I think pair-programming also includes the combination of 2 developers to code as they brainstorm.
is it possible to provide a list of these cheatsheets?