Add --whitelist flag to better/edit to signal that a tracker should be copied to /whitelist instead of /trackers
Using whitelist as the tracker category path (the current method) doesn’t work and gives the following error:
Preparing s3.amazonaws.com for editing in whitelist…
· Ensuring content working copy is clean.
· Ensuring an issue exists for: Whitelist: s3.amazonaws.com
· Issue does not exist. Creating issue: ‘Whitelist: s3.amazonaws.com’
· Ensuring a branch exists for: source.ind.ie/better/content/issues/34.
· Remote branch does not exist for: source.ind.ie/better/content/issues/34.
· Making sure a local branch does not exist either.
· Local branch also does not exist.
· Creating branch source.ind.ie/better/content/issues/34.
Switched to a new branch 'source.ind.ie/better/content/issues/34'
· Copying s3.amazonaws.com from drafts/whitelist to content/whitelist in source.ind.ie/better/content/issues/34.
cp: /Users/aral/better.fyi/drafts/whitelist/s3.amazonaws.com: No such file or directory