I just had to set up Jenkins to use GitHub. My notes (to myself, mostly):
For setting up Jenkins to build GitHub projects. This assumes some ability to manage Jenkins, use the command line, set up a utility LDAP account, etc. Please share or improve this Gist as needed.
Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist.
Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).
| #!/usr/bin/python | |
| # -*- coding: utf-8 -*- | |
| # Python script to find the largest files in a git repository. | |
| # The general method is based on the script in this blog post: | |
| # http://stubbisms.wordpress.com/2009/07/10/git-script-to-show-largest-pack-objects-and-trim-your-waist-line/ | |
| # | |
| # The above script worked for me, but was very slow on my 11GB repository. This version has a bunch | |
| # of changes to speed things up to a more reasonable time. It takes less than a minute on repos with 250K objects. | |
| # |
I could not find a proper, detailed (and up-to-date) reverse-engineerment
of Omegle's text chat protocol on the internet, so here, have one made by analyzing the web app (web requests and source code).
The responses are beautified and the query strings split up and URI-decoded for
readability.
Note that "query string" refers to parameters encoded into the URL and
"form data" to parameters in the POST body which do not have to be URI-encoded.
TODO:
| function simulateDragDrop(sourceNode, destinationNode) { | |
| var EVENT_TYPES = { | |
| DRAG_END: 'dragend', | |
| DRAG_START: 'dragstart', | |
| DROP: 'drop' | |
| } | |
| function createCustomEvent(type) { | |
| var event = new CustomEvent("CustomEvent") | |
| event.initCustomEvent(type, true, true, null) |
| ############################################################################# | |
| # | |
| # Compiled by BeS 9/15/2015 | |
| # | |
| # IBM 1047 - Code page EBCDIC (Mainframe System Z MVS z/os OS/390) | |
| # | |
| # references | |
| # https://www-01.ibm.com/software/globalization/ccsid/ccsid1047.html | |
| # http://www.kreativekorp.com/charset/encoding.php?name=CP1047 | |
| # http://www-03.ibm.com/systems/z/os/zos/features/unix/bpxa1p03.html |
While tests run in source order, surrounding code does not which can lead to hard to debug issues.
Compare the test file below with the sample output below that and note the order of the log messages.
it, beforeAll, afterAll, beforeEach or afterEach runs immediately on initialisation.
If you hate git submodule, then you may want to give git subtree a try.
When you want to use a subtree, you add the subtree to an existing repository where the subtree is a reference to another repository url and branch/tag. This add command adds all the code and files into the main repository locally; it's not just a reference to a remote repo.
When you stage and commit files for the main repo, it will add all of the remote files in the same operation. The subtree checkout will pull all the files in one pass, so there is no need to try and connect to another repo to get the portion of subtree files, because they were already included in the main repo.
Let's say you already have a git repository with at least one commit. You can add another repository into this respository like this:
| // https://github.com/Microsoft/TypeScript/issues/16577#issuecomment-343699395 | |
| const path = require('path'); | |
| const ts = require('typescript'); | |
| const { isImportDeclaration, isExportDeclaration, isStringLiteral } = require('tsutils/typeguard/node'); | |
| function getCustomTransformers() { | |
| return { before: [stripJsExt] } | |
| function stripJsExt(context) { |