This repository was archived by the owner on Oct 28, 2022. It is now read-only.
Open
Conversation
added 3 commits
February 4, 2022 17:50
returned board_data api call to its former form for backwards compatibility. It is uncler if Zenhub will continue to support that call - but it is currently working.
Owner
|
Thank you for your patch! |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Zenhub has added an API endpoint to fetch board data for a workspace.
Their documentation references this new endpoint:
GET /p2/workspaces/:workspace_id/repositories/:repo_id/boardfor returning a "ZenHub Board for a repository". I thought they had replaced the old endpoint:
GET /p1/repositories/:repo_id/boardbut it turns out it is listed under "Get the oldest Zenhub board for a repository" and still works, but will not return what you are expecting if you have multiple boards/workspaces.
This PR adds an api call to use the new endpoint which I needed.