We’re introducing calendar-based versioning for our REST API, so we can keep evolving our API, whilst still giving integrators a smooth migration path and plenty of time to update their integrations.
Impact Graphs got a nice upgrade today that has resulted in improved render times (except on the very first load after the recent deploy). Once a graph has been generated, subsequent pageloads will simply look up the cached data and send that to your browser. If you load the page and the graph is more than a day old, we’ll fire off a background job that will bring it up to date. With the new data available, subsequent loads will show the newest data. Speedy access for all!
You’ll also notice that this means that you can see the Impact Graph for even very large or old repositories like the Rails graph below.
This makes it easy to see how git preserves the author of contributions. Once Rails moved to git and GitHub, their graph explodes with attributed commits. Just another way that git says “I love you.”