Hands-on GitHub Actions (Getting Started with GitHub Actions Workflows)

This research covers the complete period from 2008, when AaronSwartz first joined GitHub, to just a few days before his death in Jan-uary 2013. It includes, where available, relevant entries from his blog forcontext (later entitled Raw thought) and other sources.

Say you have a bug report or feature request to make to a package.How can you use information on GitHub to manage your expectations (will there be a quick fix) and actions (should you go ahead and fork the repository)?In this post, we shall go over sources of information and explain how they can be used.In the end, there is no magical recipe, except perhaps graciousness, as software is made by humans.

Technology fails – at least sometimes. This is particularly true for a modern distributed research infrastructure, such as DARIAH-DE. For the operation of this infrastructure, we have implemented a monitoring solution with Icinga. This enables us to be informed about problems and react quickly.

The github repository will serve as a location for you to turn-in your homework, and allow the instructors to push back code modifications and suggestions.

There is an excellent post on open science, prestige economies, and the social web over at Marciovm's posterous*. For those of you who aren't insanely nerdy** GitHub is… well… let's just call it a very impressive collaborative tool for developing and sharing software***. But don't worry, you don't need to spend your days tied to a computer […]

Some time ago, the brilliant GitHub people gave me the following tip. Rajarshi is lazy, and might find it interesting. By appending .patch to the commit URL, a commit can easily be downloaded as patch. That way, developers can easily download it with wget or curl and apply it locally with git am, without having the fetch the full repository.