List of features for the next big release

[mislav]

Here's what I want in hub 2.3.0 (we could even tag it 3.0.0, considering the volume of changes):

• improve help system by splitting into individual man pages Split help into individual man pages #1087
  • tweak release process to auto-build and package man pages
• release command graduated from beta Big overhaul of hub release command #1095
• issue command graduated from beta Revamp hub issue commands #1099
  • make an equivalent command to list pull requests List pull requests again #1303
  • add missing filtering and sorting options to issue listing Add missing filters when listing issues. #1234
  • add an option to limit the number of results
  • add ability to list issues/pulls a la Dashboard, i.e. across a whole org, or all belonging to you add command to list pull requests in the current main project, or optionally main project organisation #1224
  • add caching locally and fetch only records updated since last cache
• improve detecting of pull-request head & base pull-request uses wrong base #461 pull-request for unpushed branch opens message editor with unrelated remote #877 Hub pull-request doesn't take GitHub repository settings into account #814 Feature to exercise #877 #1239
  • better handling of unpushed branches Hub complains of commits not yet pushed but there are none #1130
  • option to auto-push changes to a remote before opening the PR pull-request should create the remote branch if it doesn't already exist #165
  • option to create the PR using the web interface Add option for creating PR using the web interface #1005 Open the GitHub web interface to create the new pull request #688
  • improve support for forks named differently than parent repo
• enable passing milestone title instead of number to issue create, pull-request Getting an error when trying to set milestone #1089
• commands that output a URL of created resource (pull-request, issue create, release create) should have an option to copy the URL to clipboard print resultant url to stdout on successful 'hub create' #1111 pull-request should copy the pull URL to clipboard #182 Enable copy to clipboard functionality for commands that print URLs #1264
• add support for issue/PR templates Issue and Pull Request Templates, with addendums #1187 Support Pull Request and issue template #1145 Add support to pull-request template like web interface #1118 Feature: Allow a configuration setting to set a markdown template for pull requests #937
  • add support for interactively editing a template file passed in using -F Add -e option to pull request #924
  • prepare pull request message hook prepare pull request message hook #1179 pre-pull-request hook? #1174
• dedicated command for authentication & configuration Dedicated command for authentication & configuration #225 Add user command #992
  • add system for per-command default configuration Default Config #964 feature request: automatic create repository as private #1194 Feature request: Make 'origin' remote name configurable. #720
  • enable passing in Personal Access token, mostly for GHE users who don't have the option to authenticate using username/password
  • retire git config --get-all hub.host configuration
  • add global --repo OWNER/NAME argument that lets you perform operations a repo other than the directory you're currently in
  • add global --host HOST argument that changes the default github.com host and eliminate the interactive host picker Add default host as configuration option (hub.defaultHost) #1184
  • add support for XDG Base Directory spec Use XDG Base Directory Spec for default config file.  #1061
• retire browse command in favor of open command that takes one argument and automatically figures out whether it's a branch, commit, subpage, or other kind of resource to navigate to Add hub show for commits #382 Adds a flag to hub browse to choose whether to open the current or … #1112 hub browse should directly open the pull request page #1107 New command/option to open an existing pull request #897 Alias "browse" as "open" #782 Allow hub browse to accept remote as parameter #723 Would like to open user page #602
• reimplement checkout command to fetch refs/pull/XY/head instead of adding a git remote Prune obsolete/missing config after hub-checkout #1069 Pull request checkout with no 'leftovers' #1206 hub checkout <PR url> fail with private mode #1133 hub checkout argument to define the way the remote is added #1236 Reimplement hub checkout to avoid creating unnecessary remotes #1235
• improve upstream vs origin remote naming in clone, fork, etc. Renamed origin as upstream in git fork #798 FR: set upstream remote when cloning a forked repo. #811 hub remote add should offer an option to set the remote name manually #1271
  • add fork option to provide custom remote name add option to hub fork to set the name of the remote that is created #762
  • add fork option to provide custom name for new repo hub fork <new repo name> #697
• improve create ORG/NAME by requesting a team name to create the repo under if necessary hub create ORGANIZATION/NAME cannot set team_id #431
  • optional org argument to creategit create org/ to create within the org with the current directory's name #1408
  • optional org argument to fork Feature request: optional organization argument to fork, etc. #505
• implement sync command Add command to clean all merged branches #906 GitHub for Mac style sync? #618
• new search command? Possible feature: "search" command #833
• low-level api command for manual API access Data dump for consumers #1407
• add option to open failing ci-status check in browser Enhance ci-status #449

The new --format option is pretty rad:

[DanyC97]

great work @mislav !! any rough timeline when you planning to finish release the above goodies ?

[mislav]

@DanyC97 All from the above list won't all make it to the very next release, but I'm planning to release 2.3.0 this month. Check out the existing prerelease builds in the Releases section.

[igorsantos07]

Hello there! Any plans for a new release? I just noticed I was missing the important PR template my team uses by using hub to create PRs on the command line... I'm on 2.3.0, and it seems that feature got merged more than a year ago 😅

[elliott-beach]

This is an important question. I would also like to know what changes are necessary to release a new version.

[igorsantos07]

Well, it seems that feature I mentioned is indeed working; I probably used -m that bypassed the template. Should hub warn on these cases? 🤔

[mislav]

Hi everyone; thanks for your patience. My proposed feature set for 2.3.0 was overly ambitious and I've missed the schedule I have set for myself earlier this year. This is because of the two most important features for 2.3.0 (dedicated command for authentication & configuration, improving pull-request handling of head/base detection) are also the most tricky ones to implement, and I'm the only one working on hub maintenance lately.

I'm still slowly heading towards a release, and since Projects have shipped since I've opened this tracking issue, I've moved the remaining TODO items to a new Project so they can be tracked there. As always, you can test out the latest features by grabbing one of the prereleases from the Releases section.

I'm gonna close this issue out in favor of the Project board. I'll be posting this thread if there are any big updates in the future.

@igorsantos07: Indeed, the -m flag bypasses the template, as does any other option in which you explicitly provide the text for the pull request. The template is only rendered in your text editor when there is no explicit PR subject/message provided. This is by design: we want to be able to skip the template for the purpose of automation (i.e. explicit arguments should always be taken verbatim and "win" over implicit defaults).