Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
pytreat-practicals-2020
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
FSL
pytreat-practicals-2020
Commits
e74965d4
Commit
e74965d4
authored
5 years ago
by
Paul McCarthy
Browse files
Options
Downloads
Plain Diff
Merge branch 'doc/instructions' into 'master'
more instructions See merge request
!4
parents
28f99c95
cd002108
No related branches found
Branches containing commit
No related tags found
1 merge request
!4
more instructions
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+71
-25
71 additions, 25 deletions
README.md
with
71 additions
and
25 deletions
README.md
+
71
−
25
View file @
e74965d4
...
@@ -65,16 +65,48 @@ https://git.fmrib.ox.ac.uk/fsl/pytreat-practicals-2020
...
@@ -65,16 +65,48 @@ https://git.fmrib.ox.ac.uk/fsl/pytreat-practicals-2020
Updates to the master branch should occur via merge requests. You can choose
Updates to the master branch should occur via merge requests. You can choose
to either work on a
fork of
this repository, or on a
branch in
this
to either work on a
branch within
this repository, or on a
fork of
this
repository.
To contribute to the practicals using a fork:
repository.
### Using a branch within this repository
1.
Make a local clone of the repository:
```
git clone https://git.fmrib.ox.ac.uk/fsl/pytreat-practicals-2020.git
```
2.
Create a branch for your work:
```
git checkout -b my_cool_branch origin/master
```
3.
Make your changes on this branch.
```
git add <my_new_and_changed_files>
git commit -m 'super cool updates'
```
4.
Push your changes to the gitlab repository:
```
git push origin my_cool_branch
```
5.
In gitlab, submit a merge request from your branch onto the master
branch.
### Using a fork of this repository
1.
Fork the upstream repository on gitlab
1.
Fork the upstream repository on gitlab
2.
Make a local clone of your fork:
2.
Make a local clone of your fork:
```
```
git clone https://git.fmrib.ox.ac.uk/
fsl
/pytreat-practicals-2020.git
git clone https://git.fmrib.ox.ac.uk/
<your_username>
/pytreat-practicals-2020.git
```
```
3.
Add the upstream repository as a remote:
3.
Add the upstream repository as a remote:
...
@@ -85,6 +117,11 @@ repository. To contribute to the practicals using a fork:
...
@@ -85,6 +117,11 @@ repository. To contribute to the practicals using a fork:
4.
Make your changes on your local repository
4.
Make your changes on your local repository
```
git add <my_new_and_changed_files>
git commit -m 'super cool updates'
```
5.
Push your changes to your fork:
5.
Push your changes to your fork:
```
```
...
@@ -95,40 +132,49 @@ repository. To contribute to the practicals using a fork:
...
@@ -95,40 +132,49 @@ repository. To contribute to the practicals using a fork:
repository.
repository.
Or, to contribute via a branch:
### Updating your local repository
1.
Make a local clone of the repository:
To bring in the changes that other people have contributed to the main
repository into your local repository:
```
git clone https://git.fmrib.ox.ac.uk/fsl/pytreat-practicals-2020.git
```
2.
Create a branch for your work:
```
git fetch --all
```
# make sure you are on the correct local branch - if you followed the
git checkout -b my_cool_branch origin/master
# instructions above and are working on a fork of the main repository:
```
git checkout master
3.
Make your changes on this branch.
# Or if you are working on a branch within the main repository:
git checkout my_cool_branch
4.
Push your changes to the gitlab repository:
# Do this if you are working on a fork of the main repository
git merge upstream/master
```
# Or do this if you are working on a branch within the main repository
git push origin my_cool_branch
git merge origin/master
```
```
> Or, if you are comfortable with git, `rebase` is so much cooler:
>
> ```
> git fetch --all
>
> # replace <branch_name> with your local branch name
> git checkout <remote_name>/master
>
> # replace <remote_name> with the main repository name
> git rebase <remote_name>/master
> ```
5.
In gitlab, submit a merge request from your branch onto the master
branch.
### Writing your talk as a Jupyter notebook
You may also wish to install
You may wish to install
[
`notedown`
](
https://github.com/aaren/notedown
)
:
[
`notedown`
](
https://github.com/aaren/notedown
)
:
```
```
source $FSLDIR/fslpython/bin/activate fslpython
$FSLDIR/fslpython/bin/conda install -n fslpython -c conda-forge notedown
pip install notedown
source deactivate
fslpython -m notedown
ln -s $FSLDIR/fslpython/envs/fslpython/bin/notedown $FSLDIR/bin/fslnotedown
ln -s $FSLDIR/fslpython/envs/fslpython/bin/notedown $FSLDIR/bin/fslnotedown
```
```
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment