Show HN: Git Butler – IFTTT for GitHub pull request and issue workflows
1–5 of 5 posts
Re: Show HN: Git Butler – IFTTT for GitHub pull request and issue workflows
#2This is not likely to receive permission, since this kind of thing is specifically why the trademark began being enforced—this is a service built on top of the GitHub social network. GitHub login has nothing to do with Git. GitHub issues have nothing to do with Git. GitHub's pull request API has (next to) nothing to do with Git. Trying to brand this as "Git Butler" just serves to further conflate GitHub and Git.
Re: Show HN: Git Butler – IFTTT for GitHub pull request and issue workflows
#3The Git project has a trademark policy. You need permission from them if you want to use it in your brand. This is not likely to receive permission, since this kind of thing is specifically why the trademark began being enforced—this is a service built on top of the GitHub social network. GitHub login has nothing to do with Git. GitHub issues have nothing to do with Git. GitHub's pull request API has (next to) nothin…
Re: Show HN: Git Butler – IFTTT for GitHub pull request and issue workflows
#4Re: Show HN: Git Butler – IFTTT for GitHub pull request and issue workflows
#5The Git project has a trademark policy. You need permission from them if you want to use it in your brand. This is not likely to receive permission, since this kind of thing is specifically why the trademark began being enforced—this is a service built on top of the GitHub social network. GitHub login has nothing to do with Git. GitHub issues have nothing to do with Git. GitHub's pull request API has (next to) nothin…
I was not aware. Thanks for letting me know - will look into it. I am wondering how GitHub got around that issue.