You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user I would like to list my issues in my terminal so I quickly can get a glance of the current issues
Grooming
Behaviour
(GitHub) Running git issues should print an unsorted list of the first 30 open issues. Pagination should be possible.
(Jira) Running git issues should print 30 of the Jira issues you have access to, unsorted and uncategorized. Pagination should be possible
Research / Questions
Should we support a project-key for Jira, so issues are fetched from a specific project in stead of all of them. Should the project key, be in the config or as an argument or both?
Is pagination important? If so, figure out wether or not it is possible to implement pagination for both GitHub and Jira - JOKER
Tasks
Issues does not support config, make it do so.
remove the pipe to less and more on windows. It messes up everything.
Should support a target configuration, to get the URL for your issue service
Tests needs to be cleaned up
Move GetIssuesfor the GitHub api to the new Standard
Create a GetIssue function for Jira
NOTE: None of the code in the Issue function is reusable. So this task requires a complete rewrite of the function.
The text was updated successfully, but these errors were encountered:
According to their API, when calling the get issues API, a link header will appear with the next set of issue so this base: https://api.github.com/repos/praqma/git-phlow/issues&per_page=30 will return this: https://api.github.com/repositories/79813336/issues?per_page=2&page=2
There is support for going to the last page as well.
Issue
To be able to paginate, we require state. Where should that state be and when should it reset.
suggestion
When running git issues, we save the link to the next state in an environment variable. When rerunning git issue it should not paginate. Pagination starts when either git issues next or git issue -n has been called
As a user I would like to list my issues in my terminal so I quickly can get a glance of the current issues
Grooming
Behaviour
(GitHub) Running
git issues
should print an unsorted list of the first 30 open issues. Pagination should be possible.(Jira) Running
git issues
should print 30 of the Jira issues you have access to, unsorted and uncategorized. Pagination should be possibleResearch / Questions
Should we support a project-key for Jira, so issues are fetched from a specific project in stead of all of them. Should the project key, be in the config or as an argument or both?
Is pagination important? If so, figure out wether or not it is possible to implement pagination for both GitHub and Jira - JOKER
Tasks
Issues does not support config, make it do so.
remove the pipe to less and more on windows. It messes up everything.
Should support a target configuration, to get the URL for your issue service
Tests needs to be cleaned up
Move
GetIssues
for the GitHub api to the new StandardCreate a
GetIssue
function for JiraNOTE: None of the code in the
Issue
function is reusable. So this task requires a complete rewrite of the function.The text was updated successfully, but these errors were encountered: