| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title>Game Kaboom.js</title> | |
| <style> | |
| body { | |
| margin: 0; | |
| overflow: hidden; | |
| } | |
| </style> |
| Jenkins.instance.views.each { | |
| view -> | |
| println "${view.name}" | |
| view.items.each { | |
| item -> | |
| println "\t- ${item.name}" | |
| } | |
| } | |
| return |
| /** | |
| * Enter: Asking for next, last, first, prev on a GitHub Link header | |
| * Exit: corresponding value for each link | |
| */ | |
| @Test | |
| void getLinkFromHeaderTest(){ | |
| // Prepare | |
| def gitHubHeader = """Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next", | |
| <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last", | |
| <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first", |
I will maybe someday get around to dusting off my C and making these changes myself unless someone else does it first.
Imagine a long-running development branch periodically merges from master. The
git log --graph --all --topo-order is not as simple as it could be, as of git version 1.7.10.4.
It doesn't seem like a big deal in this example, but when you're trying to follow the history trails in ASCII and you've got several different branches displayed at once, it gets difficult quickly.
I will maybe someday get around to dusting off my C and making these changes myself unless someone else does it first.
Imagine a long-running development branch periodically merges from master. The
git log --graph --all --topo-order is not as simple as it could be, as of git version 1.7.10.4.
It doesn't seem like a big deal in this example, but when you're trying to follow the history trails in ASCII and you've got several different branches displayed at once, it gets difficult quickly.