jzempel / continuity Goto Github PK

View Code? Open in Web Editor NEW

27.0 27.0 1.0 282 KB

A strategy for continuous development, inspired by GitHub Flow.

License: Other

Makefile 1.56% Shell 0.12% Python 98.32%

continuity's People

Contributors

Stargazers

Watchers

continuity's Issues

Pyinstaller Issue

Traceback (most recent call last):
  File "<string>", line 11, in <module>
  File "/private/tmp/continuity-20160927-71796-32nlb8/continuity-0.10.1/pyinstaller-3.1/PyInstaller/loader/pyimod03_importers.py", line 389, in load_module
  File "pkg_resources/__init__.py", line 68, in <module>
  File "pkg_resources/extern/__init__.py", line 60, in load_module
ImportError: The 'packaging' package is required; normally this is bundled with this package so if you get this warning, consult the packager of your distribution.
pyi_rth_pkgres returned -1

Add bash completion for git-finish

Add "review" label to GitHub issue on git-review

Invert 'git-finish' to execute from integration branch rather than issue/story branch

continuity 'git-finish' should behave like 'git-merge'

Detect github personal access token collision

Steps to duplicate:

continuity init a repo for github
delete and re-clone repo
continuity init repo for github again

Result: Invalid GitHub credentials.

Workaround: goto token settings, delete repo token, and try again.

Handle git-finish merge conflicts

Pass 'finish' command line arguments through to git-merge

I installed with brew but I see I got the issue you just fixed a few hours ago... How stable is this? Should I just clone your repo and keep pulling updates or do you have a roadmap of changes that it would be better to wait on?

I just started making a small set of tools that let me keep up with branches named like {prefix}PT12345. So I can have feat-PT12345 (for feature stories) or fix-PT12345 (for bugs) and the output from my git commands gets parsed for ^.*?PT(\d+) and injects the full story title. Currently it caches stories locally so it's not hitting PT every time you look at a list of branches. Looks like your tools have a LOT more power and I'd love to try them out :)

(And I'm glad I'm not the only one that sees the benefit of coupling all this together in a work flow.)

For posterity, here was my error that looked like it matched up with your last fix...

Traceback (most recent call last):
  File "<string>", line 16, in <module>
  File "build/build/pyi.darwin/continuity/outPYZ1.pyz/continuity.cli", line 766, in main
  File "build/build/pyi.darwin/continuity/outPYZ1.pyz/continuity.cli", line 641, in init
  File "build/build/pyi.darwin/continuity/outPYZ1.pyz/continuity.cli", line 388, in _init_github
  File "build/build/pyi.darwin/continuity/outPYZ1.pyz/continuity.github", line 474, in create_token
TypeError: unbound method _request() must be called with GitHub instance as first argument (got str instance instead)

Handle command error on branch with no configured remote

i.e. git checkout -b temp && git issue

Refactor all the things

I got a little function happy in here. Use a better CLI class inheritance model.

Add milestone info to git-issue

Explicitly import sys.exist

# git start 299
Retrieving issue EGMT-299 from JIRA for hasun...
Traceback (most recent call last):
  File "<string>", line 16, in <module>
  File "/private/tmp/continuity-oPLR/continuity-0.8.2/build/continuity/out00-PYZ.pyz/continuity.cli", line 134, in main
  File "/private/tmp/continuity-oPLR/continuity-0.8.2/build/continuity/out00-PYZ.pyz/continuity.cli.commons", line 83, in __call__
  File "/private/tmp/continuity-oPLR/continuity-0.8.2/build/continuity/out00-PYZ.pyz/continuity.cli.jira", line 359, in execute
NameError: global name 'exit' is not defined

Prevent git-finish from non-integration branch

See #2, #9, & #16.

Add git-tasks support for GitHub issues

https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments

Upgrade GitPython

To solve for gitpython-developers/GitPython#687

TypeError("PackingType of packed-Refs not understood...)

Traceback on git commit

I just did a "sudo yum update" on an ec2 instance, and now continuity is throwing this error on a git commit:

Traceback (most recent call last):
  File "/usr/bin/continuity", line 9, in <module>
    load_entry_point('continuity==0.9.8', 'console_scripts', 'continuity')()
  File "/usr/lib/python2.6/dist-packages/pkg_resources/__init__.py", line 521, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.6/dist-packages/pkg_resources/__init__.py", line 2632, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.6/dist-packages/pkg_resources/__init__.py", line 2312, in load
    return self.resolve()
  File "/usr/lib/python2.6/dist-packages/pkg_resources/__init__.py", line 2318, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python2.6/site-packages/continuity/cli/__init__.py", line 12, in <module>
    from .commons import get_commands
  File "/usr/lib/python2.6/site-packages/continuity/cli/commons.py", line 15, in <module>
    from continuity.services.commons import ServiceException
  File "/usr/lib/python2.6/site-packages/continuity/services/commons.py", line 14, in <module>
    from requests.packages.urllib3 import disable_warnings
ImportError: No module named packages.urllib3

Does this package support Python 3?

Thanks.

Add -f/--force option to git-start

...for starting from a non-integration branch.

Add -m/--message option to git-review

Handle offline command invocation

git-issues not handling unicode characters

Traceback (most recent call last):
  File "<string>", line 16, in <module>
  File "continuity/cli/__init__.py", line 134, in main
  File "continuity/cli/commons.py", line 85, in __call__
  File "continuity/cli/github.py", line 186, in execute
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2318' in position 9: ordinal not in range(128)
main returned -1

Update git-finish to merge the integration (master) branch into the issue/story branch before merging the issue/story branch back into master

https://help.github.com/articles/merging-a-pull-request
https://github.com/blog/1335-tidying-up-after-pull-requests

This mirrors the "Merging via command line" instruction provided by GitHub and should prevent the "Closed with unmerged commits" message on closed pull requests.

Add -n/--name option to git-start

Unable to interactive rebase

On attempt to git rebase -i [<commit>] with message edits.

Traceback (most recent call last):
  File "/Users/jzempel/.virtualenvs/pw/bin/continuity", line 9, in <module>
    load_entry_point('continuity==0.4.2', 'console_scripts', 'continuity')()
  File "/Users/jzempel/.virtualenvs/pw/lib/python2.7/site-packages/continuity-0.4.2-py2.7.egg/continuity/cli.py", line 795, in main
    commands[command].__call__(args)
  File "/Users/jzempel/.virtualenvs/pw/lib/python2.7/site-packages/continuity-0.4.2-py2.7.egg/continuity/cli.py", line 58, in _commit
    configuration = git.get_configuration("branch", git.branch.name)
  File "/Users/jzempel/.virtualenvs/pw/lib/python2.7/site-packages/continuity-0.4.2-py2.7.egg/continuity/git.py", line 44, in branch
    return self.repo.head.ref
  File "/Users/jzempel/.virtualenvs/pw/lib/python2.7/site-packages/GitPython-0.3.2.RC1-py2.7.egg/git/refs/symbolic.py", line 244, in _get_reference
    raise TypeError("%s is a detached symbolic reference as it points to %r" % (self, sha))
TypeError: HEAD is a detached symbolic reference as it points to 'e039ccc12c43f4b49aaac65dbbbcfb8111525160'
Could not amend commit after successfully picking e039ab5... [close #13] Remove icon
This is most likely due to an empty commit message, or the pre-commit hook
failed. If the pre-commit hook failed, you may need to resolve the issue before
you are able to reword the commit.

Update to use Pivotal Tracker REST API v5

https://www.pivotaltracker.com/help/api/rest/v5

jzempel / continuity Goto Github PK

continuity's People

Contributors

Stargazers

Watchers

continuity's Issues

Recommend Projects

Recommend Topics

Recommend Org