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
Tom Nichols
pytreat-practicals-2020
Commits
e2845c22
Commit
e2845c22
authored
7 years ago
by
Paul McCarthy
Browse files
Options
Downloads
Patches
Plain Diff
More detailed instructions
parent
e838ae0e
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+25
-4
25 additions, 4 deletions
README.md
with
25 additions
and
4 deletions
README.md
+
25
−
4
View file @
e2845c22
...
@@ -4,18 +4,39 @@
...
@@ -4,18 +4,39 @@
This repository contains Jupyter notebooks and data for the 2018 WIN PyTreat.
This repository contains Jupyter notebooks and data for the 2018 WIN PyTreat.
The
master
repository can be found at:
The
upstream
repository can be found at:
https://git.fmrib.ox.ac.uk/fsl/pytreat-2018-practicals
https://git.fmrib.ox.ac.uk/fsl/pytreat-2018-practicals
To contribute to the practicals:
To contribute to the practicals:
1.
Fork the
master
repository on gitlab
1.
Fork the
upstream
repository on gitlab
2.
Make
your changes
o
n
your fork
2.
Make
a local clone
o
f
your fork
:
3.
Submit a merge request back to the master repository
```
git clone git@git.fmrib.ox.ac.uk:<username>/pytreat-2018-practicals
```
3.
Add the upstream repository as a remote:
```
git remote add upstream git@git.fmrib.ox.ac.uk:fsl/pytreat-2018-practicals.git
```
4.
Make your changes on your local repository
5.
Rebase onto the upstream repository, and push your changes to your fork:
```
git fetch --all
git rebase upstream master
git push origin master
```
6.
In gitlab, submit a merge request from your fork back to the upstream
repository.
...
...
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