Skip to content

Commit c7933c1

Browse files
committed
add instructions
1 parent e253352 commit c7933c1

2 files changed

Lines changed: 15 additions & 4 deletions

File tree

docs/README.md

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,16 @@
1-
# Some material to accompany workshop:
1+
# Git scenarios
2+
##1. Hotfix
3+
Check out the branch *pub_kensington_arms*. Do some work on it, for example add a file for the pub in the pub directory, or change some styles. While you are working away, you are told you need to fix something on the *development* branch: You need to change the colour of the main heading to orange. How best to do that without losing your current changes?
4+
##2. I should have branched!
5+
Check out the *development* branch and look at the recent commits. You realise that the last three commits should have rather gone on a new branch *new_header_styles* with the last commit in the *development* branch being "add paragraph under heading on homepage" - you could also rename that commit to something nicer.
6+
##3. Merging
7+
You are on the *pub_kensington_arms* branch. Merge in the *development* branch.
8+
##4. Clear up that mess
9+
Check out the *cafe_btp* branch and check the recent commits. Can this be tidied up a bit?
10+
<br />
11+
<br />
12+
# Contributing to the cafes and pubs directory
13+
Below is the file structure of this repo. Let's try and add some cafes and pubs. Use the cafes/c_beatroot.html file as a template for a page about your cafe or pub. Also add it to index.html. You can also change some styles of course. Then we will somehow need to get the changes into the remote..
14+
<br />
215

3-
* Slides with intro to terms and commands, incl some visual representations
4-
* Somethinng like a 'cheat sheet': Workflows for specific situations
5-
* Instructions for the workshop
16+
![Project file structure](file_structure.jpg)

docs/file_structure.jpg

24 KB
Loading

0 commit comments

Comments
 (0)