Create Rule Page

[thomasgilmore]

Closes #136

Created Rules Page under template

Rules:
Use of - for bullets
Capital letter for TriggerMesh known elements like Bridges, Sources, Targets, use TriggerMesh and not Triggermesh.
Use 1. instead of 1. 2. 3. for lists.

Let me know if there should be any changes.

[antoineco]

@thomasgilmore95 your branch possibility needs to be rebased onto the current master branch.
Let me know if you need my help on that.

[antoineco]

Looks sensible 👍
Only one comment.

[daceynolan]

So it looks like your rules state to use - and not *, but in the changes made it looks like the bullet lists were all changed to *

Do you mind changing these to -?

[daceynolan]

Also one fun trick of closing the ticket at the same time the PR is closed is by writing

closes with your ticket URL link #136

It will look like closes #136

Then when you merge the PR the ticket is closed. :)

[antoineco]

@daceynolan the unrelated changes will automatically disappear when the branch gets rebased onto master.

[antoineco]

Not sure what happened but 32 modified files can't be right. Probably a broken rebase.

[thomasgilmore]

@antoineco Not really sure what happen with the broken rebase as well. Any tips on fixing it?

[antoineco]

On the command line that would be:

git fetch origin
git rebase origin/master
git push --force

[thomasgilmore]

Not sure if this fixes things..... let me know??

Just wanted to let you know that I did fork the repo and I'm not sure if that changes things.

my remote -v links are as follows for the project
origin https://github.com/thomasgilmore95/docs.git (fetch)
origin https://github.com/thomasgilmore95/docs.git (push)
upstream https://github.com/triggermesh/docs.git (fetch)
upstream https://github.com/triggermesh/docs.git (push)

[antoineco]

Ahhh then "origin" should have been "upstream". My bad.

You may still be able to safely reapply the same commands though.

[thomasgilmore]

I used upstream now with the same commands.

[antoineco]

Looking better! Thanks