Shell #1
sbt ~fastLinkJSShell #2
npm install
npm run devShell #1
sbt fullOptJS
npm run buildTo clean up a messy repo with duplicate annotations, use the dedicated script. It uses environment variables REPO_URL and GITHUB_TOKEN. It has two modes: dry-run and standard. The dry-run process simulates the process but does not push the results.
export REPO_URL="https://github.com/umrlastig/annotation-example.git"
export GITHUB_TOKEN="ghp_..."
sbt "backend/run --dry-run"To actually commit and push the clean repo, use:
export REPO_URL="https://github.com/umrlastig/annotation-example.git"
export GITHUB_TOKEN="ghp_..."
sbt "backend/run"- sorting of objects for annotation?
- annotated vs not annotated
- annotated link types
- annotated change types
- annotated vs not annotated
- annotated types (majority?)
- annotation conflict?
Loading_2.gif from KopiteCowboy, CC BY-SA 4.0 https://creativecommons.org/licenses/by-sa/4.0, via Wikimedia Commons