Creating a custom Git flow visualization
blog.funda.nl
blog.funda.nl
Quite nice, actually. Not open source, as it is a private side project of the company, but examples are available on GitHub (cf TFA).
Main difference is that the develop and master branch always run all the way to the top. Take any public Github repo and compare the output of beta.gitflowchart.com/ with the git-log output. It is not the same thing.
Github is "Free for open source projects", I have always wondered what definition they would use for "open source". Looked for it a few years ago, and didn't find it. Any clue on what's acceptable policy for them? Maybe they consider that public repo = open source, because code is accessible?
First of all, Github is not free for Open Source, it is free for public projects (https://github.com/pricing). Not just for OSS, if the repo is public, it is free.
Is Git Flow Chart Open Source? No, it is not. Choosing an OSS license would make it hard to make money on the plugin. On Atlassians marketplace, this means that if your project is OSS, you get it for free, but if you are a paying user of Stash, you also pay for the plugin. We want to follow the same lines with Github: public repos are free, so you can use the chart on them for free. If you pay for a private repo at GitHub, for now, you cannot use the chart. We may make it available, but at a cost. However, we do want to share the code and allow you to inspect, study and contribute improvements. The core code of Git Flow Chart is hosted on GitHub. It is a javascript library and comes with unit tests and a standalone HTML page that allows you to test improvements locally. Feel free to fork.
I'm glad to learn gitHub rephrased their offer from "free for open source" to "free for public projects", it's more straightforward.
You might want to create a LICENSE.md, or to make the following sentence stand out in your README, right now it's buried in the middle of a paragraph: "I will keep use of the plug-in free for non-commercial and personal use."
We're looking to build an AtlasBoard for our project and the ideas here are very useful. We use bitbucket, so I'm not sure how similar the APIs there are to Stash, but one would hope they are similar enough that your code points us in the right direction.
My biggest question though, is on the Github permissions. It requires read/write access on all user data (and public repositories), but I'd expect read access being all that's required.