{"action":"created","issue":{"url":"https://api.github.com/repos/bill-auger/git-branch-status/issues/8","repository_url":"https://api.github.com/repos/bill-auger/git-branch-status","labels_url":"https://api.github.com/repos/bill-auger/git-branch-status/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/bill-auger/git-branch-status/issues/8/comments","events_url":"https://api.github.com/repos/bill-auger/git-branch-status/issues/8/events","html_url":"https://github.com/bill-auger/git-branch-status/pull/8","id":392759579,"node_id":"MDExOlB1bGxSZXF1ZXN0MjM5OTYwMzE3","number":8,"title":"make it installable with npm","user":{"login":"fharper","id":1170989,"node_id":"MDQ6VXNlcjExNzA5ODk=","avatar_url":"https://avatars3.githubusercontent.com/u/1170989?v=4","gravatar_id":"","url":"https://api.github.com/users/fharper","html_url":"https://github.com/fharper","followers_url":"https://api.github.com/users/fharper/followers","following_url":"https://api.github.com/users/fharper/following{/other_user}","gists_url":"https://api.github.com/users/fharper/gists{/gist_id}","starred_url":"https://api.github.com/users/fharper/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fharper/subscriptions","organizations_url":"https://api.github.com/users/fharper/orgs","repos_url":"https://api.github.com/users/fharper/repos","events_url":"https://api.github.com/users/fharper/events{/privacy}","received_events_url":"https://api.github.com/users/fharper/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-12-19T20:10:47Z","updated_at":"2018-12-20T04:19:36Z","closed_at":null,"author_association":"NONE","pull_request":{"url":"https://api.github.com/repos/bill-auger/git-branch-status/pulls/8","html_url":"https://github.com/bill-auger/git-branch-status/pull/8","diff_url":"https://github.com/bill-auger/git-branch-status/pull/8.diff","patch_url":"https://github.com/bill-auger/git-branch-status/pull/8.patch"},"body":"I'll be more than happy to add you as an author, even giving you the ownership, or still continue to help, whatever float your boat. Thanks for this script, super useful!"},"comment":{"url":"https://api.github.com/repos/bill-auger/git-branch-status/issues/comments/448861261","html_url":"https://github.com/bill-auger/git-branch-status/pull/8#issuecomment-448861261","issue_url":"https://api.github.com/repos/bill-auger/git-branch-status/issues/8","id":448861261,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0ODg2MTI2MQ==","user":{"login":"bill-auger","id":1642691,"node_id":"MDQ6VXNlcjE2NDI2OTE=","avatar_url":"https://avatars3.githubusercontent.com/u/1642691?v=4","gravatar_id":"","url":"https://api.github.com/users/bill-auger","html_url":"https://github.com/bill-auger","followers_url":"https://api.github.com/users/bill-auger/followers","following_url":"https://api.github.com/users/bill-auger/following{/other_user}","gists_url":"https://api.github.com/users/bill-auger/gists{/gist_id}","starred_url":"https://api.github.com/users/bill-auger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bill-auger/subscriptions","organizations_url":"https://api.github.com/users/bill-auger/orgs","repos_url":"https://api.github.com/users/bill-auger/repos","events_url":"https://api.github.com/users/bill-auger/events{/privacy}","received_events_url":"https://api.github.com/users/bill-auger/received_events","type":"User","site_admin":false},"created_at":"2018-12-20T04:19:35Z","updated_at":"2018-12-20T04:19:35Z","author_association":"OWNER","body":"awesome dude, it is nice to see people interested in distributing this script through other channels; but i really dont see how NPM is suitable for a shell script - isn't NPM for javascript? - if so, then why not rubygems, PIP, PECL or any other specialized package manager?\r\n\r\nan interesting idea though - generally, the primary purpose of package managers is to manage dependencies, not merely to simplify installation/upgrades, so it never occurred to me that packaging would be desirable to some\r\n\r\ni could see a slight convenience in packaging it for distros (deb, rpm, PKGBUILD, ebuild, nuget) - that would offer the same convenience to most everyone (not only users of a particular language-specific package manager); but this is, of course, only a single text file and probably always will be - so, regardless of whether it is packaged or not, \"installation\" will never be more complicated than typing a single command or a few mouse-clicks; and un-installing is nothing more than deleting it because it has no dependencies and nothing else depends on it\r\n\r\ne.g. any of the following would be equivalent:\r\n\r\n```\r\n$ npm install git-branch-status\r\n# apt-get install git-branch-status\r\n$ git clone https://github.com/bill-auger/git-branch-status.git\r\n$ wget https://raw.githubusercontent.com/bill-auger/git-branch-status/master/git-branch-status\r\nor simply click this link: https://raw.githubusercontent.com/bill-auger/git-branch-status/master/git-branch-status\r\n```\r\n\r\nthe only slight advantage i see, would be that package managers could apply upgrades automatically (presuming that the maintainers stay on top of it) - still, upgrading is only a single command, regardless of whether it is packaged or not - e.g. any of the following would be sufficient to upgrade to a new version:\r\n\r\n```\r\n$ npm update git-branch-status\r\n# apt-get upgrade\r\n$ git pull https://github.com/bill-auger/git-branch-status.git\r\n$ wget https://raw.githubusercontent.com/bill-auger/git-branch-status/master/git-branch-status\r\nor simply click this link: https://raw.githubusercontent.com/bill-auger/git-branch-status/master/git-branch-status\r\n```\r\n\r\nmouse users can upgrade simply by bookmarking the URL to the raw text file in their web browser - i guess i am too accustomed to a keybaord-centric workflow and assume (perhaps incorrectly) that most people who use git (and git-branch-status) are also - maybe there should be GUI version of git-branch-status? - that would be a good candidate for packaging as it would have dependencies\r\n\r\nin any case, i normally do not include any packaging metadata files in releases (aka. the git 'master' branch); but put them on a separate 'packaging' branch as these are not interesting generally to fownstreams or users\r\n\r\nim not saying no, but if i do this, i would want to do a thorough job and package for distros as well - are you certain that NPM would even accept a shell script?\r\n"}}
{"actor":{"display_login":"bill-auger"}}