Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
git-seminar
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Model registry
Analyze
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
Scientific Computing
education
git-seminar
Commits
1cfe59fd
Unverified
Commit
1cfe59fd
authored
5 years ago
by
ck85nori
Browse files
Options
Downloads
Patches
Plain Diff
cleans up collab in day 1 as prep for day 2
parent
1ca9800e
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
basics.html
+49
-50
49 additions, 50 deletions
basics.html
with
49 additions
and
50 deletions
basics.html
+
49
−
50
View file @
1cfe59fd
...
@@ -38,6 +38,7 @@
...
@@ -38,6 +38,7 @@
- log in to git.idiv.de
- log in to git.idiv.de
- cheat sheets are handed out later
- cheat sheets are handed out later
- if you have questions feel free to interrupt
- if you have questions feel free to interrupt
- cleanup https://git.idiv.de/sc/edu/git-merge-conflict-demo
</section>
</section>
<section
id=
"intro-objectives"
data-markdown
>
<section
id=
"intro-objectives"
data-markdown
>
...
@@ -939,15 +940,8 @@
...
@@ -939,15 +940,8 @@
- collaboration happens in issues and MR discussion!
- collaboration happens in issues and MR discussion!
- we: review and possible resolve merge request in GL
- we: review and possible resolve merge request in GL
- show next slide once merging is done on command line
- show next slide once merging is done on command line
</section>
<section
id=
"collab-maintainer"
data-markdown
>
## view of maintainer

notes:
- we: review one MR, show line comments in GL, thumbs up
- we: review one MR, show line comments in GL, thumbs up
- tomorrow: view of maintainer
</section>
</section>
<section
id=
"collab-review-criticism"
data-markdown
>
<section
id=
"collab-review-criticism"
data-markdown
>
...
@@ -967,44 +961,8 @@
...
@@ -967,44 +961,8 @@
discussion
discussion
</section>
</section>
<section
id=
"collab-review-code-of-conduct"
data-markdown
>
<section
id=
"collab-conflicts-contributor"
data-markdown
>
## review
### code of conduct
1. be friendly
1. be responsible
1. be open
1. be proactive
notes:
- the discussions are usually public, so be aware of that
- usually needed when community grows
- decide with your community, write `CONTRIBUTING.md`
</section>
<section
id=
"collab-review-your-turn"
data-markdown
>
## review
### your turn
1. review a merge request
1. discuss / emote
1. comment on code
</section>
<section
id=
"collab-conflicts"
data-markdown
>
## resolving conflicts
## resolving conflicts
### maintainer
```bash
git remote add alice https://...
git fetch alice
git switch master
git merge alice/topic/feature
# fix conflicts
git push
```
### contributor
```bash
```bash
git fetch upstream
git fetch upstream
...
@@ -1015,17 +973,21 @@
...
@@ -1015,17 +973,21 @@
```
```
notes:
notes:
- hopefully conflicting changes
- https://git.idiv.de/sc/edu/git-merge-conflict-demo
- MR status should show that (can not be merged without conflicts)
- contains two conflicting branches
- maintainer decides if trivial or delegate to contributor
- git lol
- git fetch
- explain different solutions
- create MR
- MR status show merge conflicts
- edit file, show how to keep both ours and theirs
</section>
</section>
<section
id=
"summary-3"
data-markdown
>
<section
id=
"summary-3"
data-markdown
>
## you can now
## you can now
- create and connect to remotes
- create and connect to remotes
- contribute to projects you do not own
- contribute to projects
- maintain projects you own
</section>
</section>
<section
id=
"summary-4"
data-markdown
>
<section
id=
"summary-4"
data-markdown
>
...
@@ -1120,6 +1082,43 @@
...
@@ -1120,6 +1082,43 @@
git push --force
git push --force
```
```
</section>
</section>
<section
id=
"collab-maintainer"
data-markdown
>
## view of maintainer

</section>
<section
id=
"collab-review-code-of-conduct"
data-markdown
>
## review
### code of conduct
1. be friendly
1. be responsible
1. be open
1. be proactive
notes:
- the discussions are usually public, so be aware of that
- usually needed when community grows
- decide with your community, write `CONTRIBUTING.md`
</section>
<section
id=
"collab-conflicts-maintainer"
data-markdown
>
## resolving conflicts
```bash
git remote add alice https://...
git fetch alice
git switch master
git merge alice/topic/feature
# fix conflicts
git push
```
notes:
- maintainer decides if trivial or delegate to contributor
</section>
</section>
</section>
</div>
</div>
</div>
</div>
...
...
This diff is collapsed.
Click to expand it.
Dirk Sarpe
@dsarpe
mentioned in issue
#52 (closed)
·
5 years ago
mentioned in issue
#52 (closed)
mentioned in issue #52
Toggle commit list
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