v2.1.3

Changelog

Fixes

Fix error reading template from path

Verify the template is a regular file so that the content of the template can be added to the message of the issue or pull request.

The current implementation of templates does not support directories of templates.

Fix issue update regressions

A name error was raised when using the command issue update.

This is a regression introduced in v1.1.0.

v2.1.2

Changelog

This this a small fixes release but has a couple of important changes in terms of releases themselves. Pre-built packages were provided in the past via Bintray and attached to GitHub releases.

Bintray is dead, so obviously we are not publishing packages there anymore. We are also not providing pre-built built packages in the GitHub releases for now, but that could be back in the future. The good news is the Debian packages was updated to the previous latest release, so it shouldn't be too hard to keep up to date via the official channel anyway.

Milestone details.

Bug fixes

Fix typos

Some typos in the output and man page were fixed.

v2.1.1

Release Notes

Bugs fixed

Check if the base branch exists when creating a PR (#92)

When creating a PR if the specified (or inferred) base branch doesn't
exist, a very weird error message was printed. Now the branch existence
is explicitly checked before attempting the PR creation.

v2.1.0

Changelog

New Features

A script can now be defined to run on certain events (hooks)

When the hub.hookscript git configuration is present, it will be used as a script to run on certain events. For now this feature is considered experimental and only the postclone event is defined. Please have a look at the HOOK SCRIPT section in the man for details.

Migration notes

No last resort default for pull new/attach --base

The old master default made little sense, as repositories sometimes have a different default branch, or have no master at all. Now that GitHub have changed the default branch to main for new projects (and many projects are moving away from using master as a name for anything altogether) it makes less sense that ever to use this last resort default.

An error will be shown if the pull new or pull attach commands have no remote tracking branch or a hub.pullbase configuration is present. If you relied on this behaviour just do: git config hub.pullbase master (add --global to set this default globally for all your repos).

v2.0.3

Changelog

Bugs fixed

The setup command will not attempt to login using user/password

GitHub stopped supporting logins using user/password with the API, so trying to do so in the setup command is doomed to fail. Because of this, support for generating a Personal Access Token (PAT) for the user is now removed. Instead the user has to create their own PAT manually and pass it to the setup command instead.

In particular the setup command removed the --password option and added the --oauthtoken option instead, and when not specified, it will ask the user to create one (with some hints on how to do so).

NOTE: This would normally be a breaking change deserving a new major release, but since the tool was externally broken, there is no way to fix it without breaking changes and previous versions will be all broken, so it doesn't make sense to make a major release for this change.

v2.0.2

Changelog

Bugs fixed

Fix typo in the man page

There was a typo in the example on how to enable syntax highlight in VIM.

v2.0.1

Changelog

Bugs fixed

PGP signatures of commits are not included in messages anymore

When creating a pull request or using a commit message in any way, if the
commit was PGP-signed and the user had git configured to always show signatures
(git config log.showsignature=true), then the message would include the
signature verification text, which is not really something you usually want to
include.

Now --no-show-signature is always used when retrieving commit messages.

v2.0.0: The Future (Python3) is here

Changelog

Debian packages: https://bintray.com/sociomantic-tsunami/tools/git-hub/v2.0.0

Migration

Python version 3 required

git-hub has been ported to Python 3.

As development of Python ended January 1st 2020, the decision was made to drop backwards compatibility.

General migration instructions are given below:

- Check if **Python3** is installed by using `python --version` or check if the `python3` program exists.
- If that's not the case use your package manager to install it. E.g. `apt install python3` for **Debian** based distributions.

Use #-# for comments instead of #

The symbol # at the start of a line is a header tag in Markdown and #-#should be used instead for comments. The syntax of the new comment header does not look aesthetically good and it is not intended for practical use but it will avoid mangling markdown or any other markup language.
If you have any script that creates new issues, PRs or comments then they will need to be updated to the new comment header.

New Features

Allow specifying a command to get the oauthtoken

Sometimes storing OAuth token in plain text is not a great idea, so now the oauthtoken configuration variable can use a shell command to get the token instead. Just prepend a ! and write the command you want to run instead of using the token.

For example:

git config hub.oauthtoken '!password-manager ~/my.db get github-oauth-token'

Support issue and pull request templates

• The commands git-hub issue new and git-hub pull new add template contents to the issue or pull request message respectively.

Looks for a template file in the root directory of the project, the .github directory and the .git directory until the first template file is found. Then reads the content from the template file found and adds it to the message of the issue or pull request.

The supported file names for issue templates are ISSUE_TEMPLATE and ISSUE_TEMPLATE.md, and for pull request templates are PULL_REQUEST_TEMPLATE and PULL_REQUEST_TEMPLATE.md.

The order for template lookups matters meaning that a template file name without extension is looked up first followed by the template file name with extension .md.

Note that only the content of the first issue or pull request template found is added to the message of the issue or pull request respectively.

Finally the commands git-hub issue new and git-hub pull new also accept --no-template to skip adding the template content to the issue or pull request message respectively.

Details

• Merge tag 'v1.1.1' into v2.x.x (34c4ff1)
• Update release notes (781f4f2)
• Fix unicode in PR title or description (50c94dc)
• Decode bytes before using them as a string (66fd0e4)
• Add release notes for oauthtoken commands (c035103)
• Remove oauthtokencmd config and use oauthtoken (2eb0c58)
• Add option to retrieve oauthtoken from a password store (1bc119e)
• Add Debian package badge (00561d7)
• Remove trailing spaces (0c5290a)
• Add llucax (myself) to the FUNDING.yml file (5af7cb7)
• Add release notes for python3 migration (139f09b)
• Support issue and pull request templates (8964c1c)
• Fix beaver build cmd (ccdf659)
• Update python dependency in README (d46a87f)
• Refactor filtering in IssueCmd (b9db8e1)
• Remove duplicate imports (9f30d89)
• Change hardcoded python2 to python3 (02339a6)
• Change default python version to python3 in Makefile (357dac0)
• Port git-hub script to python 3 (c376fb7)
• Add a release note for the new comment header (cdece3a)
• Use #-# for comments instead of # (e38cab3)
• Clear release notes after release (2806148)

v1.1.1

Changelog

• Update release notes (781f4f2)
• Fix unicode in PR title or description (50c94dc)

https://bintray.com/sociomantic-tsunami/tools/git-hub/v1.1.1

v1.1.0: Features

Features

• Now git-hub issue update -t TITLE can be used to update issue's title.
• Now git-hub pull new accepts --labels, --milestone and --assign
• Create draft pull request
  • git-hub pull new accepts --draft or -d to create a draft pull request.

Related milestone: https://github.com/sociomantic-tsunami/git-hub/milestone/24?closed=1