Releases: sociomantic-tsunami/git-hub
Releases · sociomantic-tsunami/git-hub
v0.8.0
New Features
- Ask for the final v3 GitHub API version (#113)
- setup: Check for gitdir before anything else (#111)
- setup: Use the configured username if present (#103)
- setup: Add limited support for login using the e-mail (#102)
- setup: Improve error message for non-global setup (#100)
- clone: Accept an HTTP URL as a repository location (#97, #95)
- pull: Add info about the pull request base/head for new/attach (#114)
- pull: Add a warning when rebasing a PR that is not passing the tests (#88)
Bug Fixes
v0.7.2
v0.7.1
v0.7.0
Major changes in this version:
pull rebase
now doesn't stash everything (even untracked files) by default, if you want to use the old behaviour, use the new--stash-all
option (or--stash-include-untracked
for a less extreme alternative) (#22)clone
can now set up a triangular workflow for you, just use the--triangular
option (#64)clone
now can forward options togit clone
, so you can pass any Git option (like--recurse-submodules
) when cloning from GitHub (#69)issue show
andpull show
have been greatly improved and now shows all the comments, labels and status, use the new option--summary
to get the old short format (#76, thanks @matthiasbeyer!)
A bunch of small improvements and bugfixes were also added:
- Fixed retrieval of empty lists (issues/pull requests) (2cd9949)
- Documentation and info messages fixes and improvements (#70, #71, #78)
- Switched to use GitHub media type v3, as the old one is deprecated and not longer the default (#80)
- Fixed and improved verbose/debug output (33ee418, 435fcad, d8864c5)
- Now fpm is used to generate the Debian package, a proper package with Debian tools is left out for an eventual DD that wants to do a proper package (#68)
- Now is easier to customize the Python interpreter to be used at build time (fa217b5)
v0.6.0
This release only include one small improvement in the man page compared to v0.6.0-rc1. Here is the complete changelog since version 0.5.0:
- Add a small comment on pull attach permissions in the man page (it can
only be used if you are assigned to the issue or you have write access to
the repo) (#66) - GitHub Enterprise and other non-standard GitHub locations are now
supported by making the GitHub API base URL configurable viagit config hub.baseurl
(#51) pull rebase
now forces the rebasing by default. This means the Committer
and CommitDate metadata is updated in all the rebased commits (even if the
rebase could be just a fast-forward merge). This way the information about
who, what and when stuff got "merged" doesn't get lost.
If you want to go back to the previous default, set thegit config hub.forcerebase
tofalse
. Also, to avoid confusion, the option
--force
was renamed to--force-push
and the short alias-f
was
removed, as it shouldn't be a common operation in a rebase (#59)pull new
andpull attach
got the option--force
renamed to
--force-push
to match the new name inpull rebase
(#59)- GitHub results are now fully retrieved (before if there were too many
results from a query, the query was only partially retrieved) (#61) - A serious encoding problem was fixed. This only manifested when the title
of an issue was longer than 60 characters (#60) - If there are GitHub errors while rebasing, now more information is printed
to ease the debugging (#57) - Several code cleanups and minor fixes (ef94d4b, d711c65, d39bbb9, 6f63324,
bb83bd5, 7f027bb, 6cfc205)
v0.6.0-rc1
- GitHub Enterprise and other non-standard GitHub locations are now
supported by making the GitHub API base URL configurable viagit config hub.baseurl
(#51) pull rebase
now forces the rebasing by default. This means the Committer
and CommitDate metadata is updated in all the rebased commits (even if the
rebase could be just a fast-forward merge). This way the information about
who, what and when stuff got "merged" doesn't get lost.
If you want to go back to the previous default, set thegit config hub.forcerebase
tofalse
. Also, to avoid confusion, the option
--force
was renamed to--force-push
and the short alias-f
was
removed, as it shouldn't be a common operation in a rebase (#59)pull new
andpull attach
got the option--force
renamed to
--force-push
to match the new name inpull rebase
(#59)- GitHub results are now fully retrieved (before if there were too many
results from a query, the query was only partially retrieved) (#61) - A serious encoding problem was fixed. This only manifested when the title
of an issue was longer than 60 characters (#60) - If there are GitHub errors while rebasing, now more information is printed
to ease the debugging (#57) - Several code cleanups and minor fixes (ef94d4b, d711c65, d39bbb9, 6f63324,
bb83bd5, 7f027bb, 6cfc205)
v0.5
v0.5rc2
v0.5rc1
- Add a new
pull checkout
command to easily checkout a pull request. This
is just a wrapper to the standard checkout command, but fetches and
automatically adds the head reference of the selected pull request (#29) - Add a
--pause
option topull rebase
command. This makes a pause just
before pushing the rebased result back to the repository and updating the
issue. This is similar topull checkout
very useful for testing the
exact result of the rebase (#39, #44, 0fe1615) - Allow creating pull requests from a headless checkout as long as
--create-branch
is specified (#33) - Plus some minor bug fixes and improvements:
- Fix some unicode-related problems when unicode is present in commit
messages. Bare in mind branch names with unicode characters are still
problematic, see #46 for details (#45) - Improve warning message in
pull rebase
when not the pull request is not
in a mergeable state (495f87e) - Fix a problem with interrupted
pull rebase
while--edit-msg
is used
(#38) - Add missing documentation for
pull rebase --force
(#40) - Don't requite
hub.upstream
configuration variable to be set for
clone
, but require authentication (#36, #32)
- Fix some unicode-related problems when unicode is present in commit