duplys / git-issues Goto Github PK

View Code? Open in Web Editor NEW

257.0 257.0 35.0 230 KB

A distributed issue tracking system based on Git repositories, written in Python

Home Page: http://www.newartisans.com

License: BSD 3-Clause "New" or "Revised" License

Python 100.00%

git-issues's People

Contributors

Stargazers

Watchers

git-issues's Issues

Getting extended comment info

Hi,
I am writing a plugin to integrate git-issues support with viewgit. I have got most things figured out, except how to get info about comments, like author and attachments. Any help you could provide would be most appreciated.

Currently I am just breaking up the filename of the comment XML file, but how do I actually get the file contents to get the tasty infos contained inside?

would you consider adding a git comment-read HASH command?

Python 3 support

What do you prefer ?
Complete removal of python 2 support and moving toward python 3 or migrating code toward support of both version ?

Make the name of the branch to use configurable

Fixing unicode resources

The following changes since commit 6995a0c2c4f5cecbeb6d20a08eb3d79b186f6fc6:

  Added note about project being defunct (2011-12-06 13:14:43 -0600)

are available in the git repository at:

  [email protected]:issue_tracking/git-issues.git unicode

for you to fetch changes up to 7bb87af464227acbc98ed0858c37df0adfff73e0:

  First attempt to make git-issues a bit more Unicode compatible. (2012-06-18 15:15:09 +0200)

----------------------------------------------------------------
Matěj Cepl (2):
      Make the program PEP8 almost compatible
      First attempt to make git-issues a bit more Unicode compatible.

 .gitignore     |    1 +
 TODO           |   40 +++++++
 git-issues     |  436 ++++++++++++++++++++++++++++++++++++++--------------------------------
 gitshelve.py   |  202 ++++++++++++++++----------------
 t_gitshelve.py |    4 +-
 5 files changed, 385 insertions(+), 298 deletions(-)
 create mode 100644 TODO

git-issues init fails when README isn't found

git-issues init fails due to a failed attempt at copying "README" into .gitissues. I guess git-issues should be updated to rather copy the file "README.textile".

README should not be required

Duplicate of issue #2 thought it seems to have come back.

I copied the script to my ~/bin directory. git init caused this traceback because it couldn't copy it's own README file into a new issues branch of a git repo. This shouldn't be required.

$ git issues init
Traceback (most recent call last):
  File "/home/user01/bin/git-issues", line 1075, in 
    copy(os.path.join(os.path.dirname(__file__), "README"), issuesdir)
  File "/usr/lib/python2.7/shutil.py", line 119, in copy
    copyfile(src, dst)
  File "/usr/lib/python2.7/shutil.py", line 82, in copyfile
    with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/home/user01/bin/README'

Allow multi-line comments

The following changes since commit f343e5c9ea7c5f35fa22747c6a6f725532569575:

  More unicode issues resolved. (2012-06-18 15:40:10 +0200)

are available in the git repository at:

  [email protected]:issue_tracking/git-issues.git multiline_comments

for you to fetch changes up to 311034ed3ca74df7a000c1c0fc7dc9f073720cf4:

  First attempt to add multiline comments. (2012-06-21 00:18:41 +0200)

----------------------------------------------------------------
Matěj Cepl (2):
      Make scripts PEP8 fully compatible.
      First attempt to add multiline comments.

 TODO       |   40 -----------------------
 git-issues |  128 ++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------
 2 files changed, 91 insertions(+), 77 deletions(-)
 delete mode 100644 TODO

eat your own dogfood

github issues on a ticket tracker? really?

Installation doc?

How about a paragraph on how/where to install this? You mention 'put a copy in your repo to keep it version-sync'd with your data' but... what kind of implications does that have on $PATH ? How would that work exactly, given multiple repos each with a potentially different version?

Python syntax error on run

I get the following error when running the script on my environment:

>git issues
  File "C:\Program Files (x86)\Git/libexec/git-core\git-issues", line 335
    print [key for key in self.shelf.iterkeys()]
                 ^
SyntaxError: invalid syntax

I'm running Python 3.4.0 on Windows 8.

How to install

my os is Ubuntu 10.04.2 LTS \n \l , I read you readme , but I don't know how to install it.

Post-receive hook?

John, way cool project!

Any self-respecting issue tracker these days needs to have a way to modify issues with checkin comments. Is that even plausible with git-issues? Ideally, you'd want to make it all part of the commit.

-Dave A

git-issues responds badly to uninitialized repository

Running git issues list before initializing a repository for git-issues results in Python traceback and git errors:

Traceback (most recent call last):
  File "/Users/lars/bin/git-issues", line 1061, in <module>
    issueSet = GitIssueSet().load_state()
  File "/Users/lars/bin/git-issues", line 412, in load_state
    cachedIssueSet = cPickle.load(fd)
  File "/Users/lars/bin/gitshelve.py", line 556, in __setstate__
    if not self.head or self.head != self.current_head():
  File "/Users/lars/bin/gitshelve.py", line 223, in current_head
    x = self.git('rev-parse', self.branch)
  File "/Users/lars/bin/gitshelve.py", line 220, in git
    return apply(git, args, kwargs)
  File "/Users/lars/bin/gitshelve.py", line 134, in git
    raise GitError(cmd, args, kwargs, err)
gitshelve.GitError: Git command failed: git rev-parse (): fatal: ambiguous argument 'issues': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

It would be friendly to catch this particular situation and give the
user a help error message ("you need to run git issues init before
using this command") or something.

git mktree error on Windows

I tried creating a new issue with git issues new "Some issue", and I got this error:

Traceback (most recent call last):
  File "[snip]\git-issues\git-issues", line 1243, in <module>
    issueSet.save_state()
  File "[snip]\git-issues\git-issues", line 438, in save_state
    self.shelf.sync()
  File "[snip]\git-issues\gitshelve.py", line 375, in sync
    self.commit()
  File "[snip]\git-issues\gitshelve.py", line 366, in commit
    tree = self.make_tree(self.objects, accumulator)
  File "[snip]\git-issues\gitshelve.py", line 338, in make_tree
    name = self.git('mktree', '-z', input=buf.getvalue())
  File "[snip]\git-issues\gitshelve.py", line 220, in git
    return apply(git, args, kwargs)
  File "[snip]\git-issues\gitshelve.py", line 134, in git
    raise GitError(cmd, args, kwargs, err)
gitshelve.GitError: Git command failed: git mktree (): fatal: path cb/4266b0c28c331fc69965b47242094468bd6f32/issue.xml contains slash

I'm running Windows 10, with Python 2.7.13. I got no such error when running Debian 8 with Python 2.7.9.

Traceback (most recent call last):
  File "/home/user01/src/git-issues-git/.gitissues/git-issues", line 1124, in 
    for comment in issue.comments])
AttributeError: GitComment instance has no attribute 'comments'

duplys / git-issues Goto Github PK

git-issues's People

Contributors

Stargazers

Watchers

Forkers

git-issues's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs