The means the sysdata file becomes out of sync with the source files. In order to make this work I have a Makefile and a couple of scripts in the ‘data-raw’ directory that create the sysdata file from the ‘adjectives.txt’ and ‘nouns.txt` files.įor the most part, this works pretty well, but I found myself frequently forgetting to update the sysdata file before committing new versions of the adjectives and nouns lists. The full contents of both lists are currently under review, but if you spot anything in either list that you think shouldn’t be there, please let me know. Note: The adjective and noun lists were built using both manual addition and web scraping approaches ( rvest for the win!). I’m not a huge fan of keeping binary objects that are updated regularly in source control, but without it I don’t think the package could be installed using the devtools::install_github() approach.
The source files and the sysdata file all live in the repo. The adjective and noun lists are just plain text files which are then used to create a R/sysdata.rda binary file. Whilst the package itself is very simple, the scaffolding around the package – particularly around the management of the adjective and noun lists – is much more substantial. It only has a single function and that function just outputs a random adjective and noun combo, like ‘unshaved-oven’. It’s a pretty silly package by most measures. One of my spare-time projects is an R package called memorids. This detail will become very important later on. The sorts of git hooks that we’re discussing here are all run locally on the system you’re working on. If the code produces an error (any non-zero exit code), then the specified action is not run and the output of your code is displayed. If your code exits cleanly (with a 0 exit code) then the specified action – such as the git push – proceeds. This could be used to test something, or post a message to slack saying: “Mark’s just pushed some code - Prepare for a broken build!” For instance you could use the ‘pre-push’ hook to trigger some code immediately prior to a git push. They’re basically bits of code that are triggered by a particular git event.
Git hooks are a built-in feature - no need to download anything. Git hooks are scripts that Git executes before or after events such as: commit, push, and receive.
0 kommentar(er)
