Closed talwrii closed 8 years ago
This pull request has far too many unrelated features for me to review. A pull request should contain commits related to one feature only and should be on a topic branch instead of master.
I'm very interested in this code, but I need it in small pull requests so that I can review and merge them more easily.
Thanks,
William
Aha, yes. I issued a pull request from master a few months ago, forgot about the merge request, and kept on adding stuff. I shall split this into a few topic branches for you. It was about one thing when I made it :P .
If I recall correctly, there were also some file renames and whitespace changes that I merged in...
That being said most of my pull requests are probably going to consist of one patch :)
Pull requests:
--format and --json options for search: https://github.com/williamh/pybugz/pull/92 --unassign option on modify: https://github.com/williamh/pybugz/pull/93 product and component commands: https://github.com/williamh/pybugz/pull/94 my preferences for bugz get (contentious): https://github.com/williamh/pybugz/pull/95 not-status search option and allow (contentious) open search: https://github.com/williamh/pybugz/pull/96
Okay I've run out of steam now. I still have patches for
The --json options makes it easier to use search results programmatically. It also acts as documentation for --format.
--format is quite useful for ad hoc querying (e.g - how many bugs does each project have, how many bugs are there of this priority etc etc)