-
Notifications
You must be signed in to change notification settings - Fork 63
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
Contribute update #121
Contribute update #121
Conversation
contribution.qmd
Outdated
@@ -12,16 +12,34 @@ Please contribute by submitting a pull request to and our team will review it. I | |||
|
|||
**Instructions for Contributions to** [**the CAMIS repository**](https://github.com/PSIAIMS/CAMIS) | |||
|
|||
1. Set up RStudio to clone the CAMIS github repo -- See this [guidance for more detail](https://github.com/PSIAIMS/CAMIS/blob/main/minutes/posts/13Feb2023_Contributing%20to%20the%20CAMIS%20project_Setting%20up%20communication%20between%20github%20and%20R%20studio.docx) | |||
The following instructions assume you have not done a contribution in the past. If you have contributed in the past skip down to step 000000 |
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.
Should this be step 5?
contribution.qmd
Outdated
|
||
2. If this is your first contribution, contact [christina.e.fillmore\@gsk.com](mailto:christina.e.fillmore@gsk.com) and give her your github username, requesting to access the CAMIS repo for contributions | ||
1. You will need to git, github, and RStudio setup to talk to each other. To do this you will need to have a github account and git installed on your computer. And then connect your computer to github, we tend to recommend using a PAT because it is bit easier than SSH. We have a script that can help you set that up, found [here](https://github.com/PSIAIMS/git-training/blob/3abcc07a37aa50be161392a0327007b92cf35f9c/git-cred.R). For more information Jenny Bryan has a great [bookdown](https://happygitwithr.com) explaining how to get setup, alternative we have a [short guidance](https://github.com/PSIAIMS/CAMIS/blob/main/minutes/posts/13Feb2023_Contributing%20to%20the%20CAMIS%20project_Setting%20up%20communication%20between%20github%20and%20R%20studio.docx). |
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.
update to:
- You will need to get git, github, and RStudio setup to talk to each other. To do this you will need to have a github account and git installed on your computer. To connect your computer to github, we tend to recommend using a PAT because it is bit easier than SSH. We have a script that can help you set that up, found here.
For more information Jenny Bryan has a great bookdown explaining how to get setup, alternatively see the following link for a short guidance.
contribution.qmd
Outdated
|
||
![](images/contributions/clone2.png) | ||
|
||
5. Go into RStudio and Create a branch -- Give you are working from you own fork, this step it is a bit optional. It is up to you if you want to make a separate branch or not. But, it is generally considered good practice, especially if you are planning on contribute regularly. To do this from RStudio click the branch button (on the git tab top right). Within the box that comes up ensure you are on the "remote=origin" and "Sync branch with remote" is checked. You can name the branch something to do with the amends you intend to make. |
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.
working from your own fork,
planning on contributing regularly.
contribution.qmd
Outdated
|
||
6. Edit and /or add files within the CAMIS directories. If you are adding SAS guidance store under sas folder, R guidance store under r folder, for "SAS vs R" comparison store under comp. Follow the naming convention of the files already stored in those folders. | ||
|
||
7. Within R studio - Commit each change or new file added, and push to the repo from within R studio. Once you have complete the change you want to make, it is time for a pull request. Before we start though, it is good to check that your branch on github contains all the update you have done. If not you may need to push from Rstudio before moving onto the pull request. |
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.
Once you have completed the change
contribution.qmd
Outdated
|
||
![This is what it will look like if you still need to push](images/contributions/push.png) | ||
|
||
8. Pull request in github - Back on your fork in github you will see that you repo is now ahead of the main CAMIS repository. The first thing you want to do is make sure there aren't any conflict that have arisen with the main repository, so you need to click 'Sync fork'. |
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.
you will see that your repo is now
No description provided.