Git Product home page Git Product logo

github's Introduction

github's People

Contributors

rsc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

github's Issues

issue: mention the need for a githubissue port

I got a panic while running issue -a.

This line failed to print the error message https://github.com/rsc/github/blob/master/issue/acme.go#L70. I eventually figured I had to add

plumb to githubissue

to ~/lib/plumbing but that's not in the documentation. The panic trace is similar to the below (similar because line number is influenced by some print's I've added).

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x230 pc=0x7b6509]

goroutine 21 [running]:
9fans.net/go/acme.(*Win).Err(...)
	/home/nicolagi/go/pkg/mod/9fans.net/[email protected]/acme/acme.go:895
main.(*awin).plumbserve(0xc0000a8480)
	/home/nicolagi/go/src/rsc.io/github/issue/acme.go:71 +0x149
created by main.acmeMode
	/home/nicolagi/go/src/rsc.io/github/issue/acme.go:62 +0x1f7

issue: allow configurable default or default to current repo origin

Currently, issue defaults to the golang/go repo and there exists no way to change this. This means those using issue and not working on that repo must frequently supply a -p user/repo. I think it would be nice if issue was a little "smarter" about the repo I'm interested in and so I propose adding smarter defaults using the following rules, each overriding the next:

  • issue commands use -p if supplied
  • issue commands default to git config github.issue.repo.always if supplied
  • issue commands default to the origin repo if supplied and its host is github
  • issue commands default to git config github.issue.repo if supplied
  • issue commands default to golang/go if none of the above are satisfied.

I'm not married to the git config names.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.