microsoft / microsoft/azure-devops-python-api
#355 seems to revert the changes made by #258 in v6.0. How can I get the continuation_token to use now in v6.0?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 684
- Forks
- 218
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 1
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue has no body and refers to changes in #355 and #258 for v6.0. Start by reading those issues and locating the v6.0 continuation_token API behavior; done would be a documented, confirmed way to use the token or a clearly scoped fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100