This repository was archived by the owner on Nov 1, 2017. It is now read-only.
Corrected milestone ref from due_date to due_on #951
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Indeed. Thanks 🍰
Also correct. 👍 |
pengwynn
added a commit
that referenced
this pull request
Jan 9, 2016
Corrected milestone ref from due_date to due_on
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The docs referred to a
due_datefield which doesn't exist. The field is actuallydue_on.Side note: The API does not return the referenced
completenessfield although apparently we can sort on it. I assumecompletenessis an internal field equalsopen_issues/ (open_issues+closed_issues), and which is not exposed via the API.