-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add typical workflow to README #654
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks Sam! 👍
README.md
Outdated
- or by [using Ruby](#running-a-task-from-ruby) | ||
3. [Monitor the Task](#monitoring-your-tasks-status) | ||
- either by using the included web UI, | ||
- or by manually checking your task's run's state in your database |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit for consistency
- or by manually checking your task's run's state in your database | |
- or by manually checking your task's run's status in your database |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- or by manually checking your task's run's state in your database | |
- or by manually checking your task's run's status in your database. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a private API, not sure we should mention it really.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair point, but I see two reasons to keep it:
- It mirrors the items above it by mentioning a non web-ui way to accomplish the task.
- In the "Monitoring your Task's status" section we give a detailed list of every single state and what it means, so it's arguably not quite totally private. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great idea, there is quite a lot of documentation at the same level of detail, and having an overview at the beginning is really useful.
README.md
Outdated
- or by [using Ruby](#running-a-task-from-ruby) | ||
3. [Monitor the Task](#monitoring-your-tasks-status) | ||
- either by using the included web UI, | ||
- or by manually checking your task's run's state in your database |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- or by manually checking your task's run's state in your database | |
- or by manually checking your task's run's status in your database. |
README.md
Outdated
- or by [using Ruby](#running-a-task-from-ruby) | ||
3. [Monitor the Task](#monitoring-your-tasks-status) | ||
- either by using the included web UI, | ||
- or by manually checking your task's run's state in your database |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a private API, not sure we should mention it really.
67f7018
to
076b6b7
Compare
I've addressed the punctuation comments. I'm going to merge leaving the database section for now to get the improved docs in; we can always iterate and remove it later if we so choose. |
Currently, it is easy to overlook the section mentioning running tasks via the web UI. By adding a typical workflow, and some section headings, we make this clearer.
076b6b7
to
240ecb3
Compare
Currently, it is easy to overlook the section mentioning running tasks via the web UI. By adding a typical workflow, and some section headings, we make this clearer.