Skip to content

Tags: sociomantic-tsunami/git-hub

Tags

v2.1.3

Toggle v2.1.3's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
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

Toggle v2.1.2's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
v2.1.2

# Changelog

## Bug fixes

### Fix typos

Some typos in the output and man page were fixed.

v2.1.1

Toggle v2.1.1's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
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

Toggle v2.1.0's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
When the `hub.hookscript` git configuration is present, it will be us…

…ed 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.

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).

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.

v2.0.0

Toggle v2.0.0's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
Version 2.0.0

v1.1.1

Toggle v1.1.1's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
Version 1.1.1

v1.1.0

Toggle v1.1.0's commit message
Features

--------

* Now `git-hub issue update -t TITLE` can be used to update issue's title.

### Create draft pull request

* `git-hub pull new` accepts `--draft` or `-d` to create a draft pull request.

* Now `git-hub pull new` accepts `--labels`, `--milestone` and `--assign`