diff --git a/.nojekyll b/.nojekyll index 0c1f1b4..ce314d0 100644 --- a/.nojekyll +++ b/.nojekyll @@ -1 +1 @@ -3c5e9d40 \ No newline at end of file +783fc651 \ No newline at end of file diff --git a/_quarto.yaml b/_quarto.yaml index 9cfddd1..e71f0ed 100644 --- a/_quarto.yaml +++ b/_quarto.yaml @@ -8,8 +8,8 @@ project: - "*.sh" - "*.yaml" website: - title: "ns-rse" - site-url: https://ns-rse.github.io/ + title: "nshephard.dev" + site-url: https://blog.nshephard.dev/ description: "Software development in a Research Environment" navbar: right: diff --git a/about-code.xml b/about-code.xml index 03f122e..7e9759d 100644 --- a/about-code.xml +++ b/about-code.xml @@ -5,21 +5,21 @@ xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"> -ns-rse -https://ns-rse.github.io/about.html#category=code - +nshephard.dev +https://blog.nshephard.dev/about.html#category=code + Software development in a Research Environment -https://ns-rse.github.io/img/profile.jpg -ns-rse -https://ns-rse.github.io/about.html#category=code +https://blog.nshephard.dev/img/profile.jpg +nshephard.dev +https://blog.nshephard.dev/about.html#category=code quarto-1.3.14 Sun, 07 May 2023 00:00:00 GMT Pre-Commit : Useful Hooks Neil Shephard - https://ns-rse.github.io/posts/pre-commit-hooks/index.html + https://blog.nshephard.dev/posts/pre-commit-hooks/index.html I’m a big fan of pre-commit and have written about it before (see posts on pre-commit, pre-commit CI and pre-commit updating). This post discusses some of the hooks that I use and how to configure them.

@@ -174,12 +174,12 @@ No matching items author = {Neil Shephard}, title = {Pre-Commit : {Useful} {Hooks}}, date = {2023-05-07}, - url = {https://ns-rse.github.io//posts/pre-commit-hooks}, + url = {https://blog.nshephard.dev//posts/pre-commit-hooks}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7, -2023. https://ns-rse.github.io//posts/pre-commit-hooks. +2023. https://blog.nshephard.dev//posts/pre-commit-hooks.
]]>
code analysis @@ -188,14 +188,14 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7, github gitlab pre-commit - https://ns-rse.github.io/posts/pre-commit-hooks/index.html + https://blog.nshephard.dev/posts/pre-commit-hooks/index.html Sun, 07 May 2023 00:00:00 GMT
Pre-Commit.ci : Integrating Pre-Commit into CI/CD Neil Shephard - https://ns-rse.github.io/posts/pre-commit-ci/index.html + https://blog.nshephard.dev/posts/pre-commit-ci/index.html “Pre-Commit : Useful Hooks.” May 7,

Setup is relatively straight-forward, head to https://pre-commit.ci and sign-in with your GitHub account and grant pre-commit.ci access to your account.

-

+

Pre-commit CI

Once you have granted access you can choose which repositories pre-commit.ci has access to. It is possible to grant access to all repositories but I would recommend doing so on a per-repository basis so you know and are in control of what is happening across your repositories. If you have administration rights to organisation repositories these should be listed in the “Select repositories” pull-down menu.

-

+

Granting pre-commit.ci access to GitHub

@@ -259,28 +259,28 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7,

When logged into pre-commit.ci using your GitHub account you are presented with a page similar to the following which lists the accounts and any organisations that you have authorised pre-commit.ci to access.

-

+

Pre-commit.ci account access

You can follow the links through to view the history of jobs run by pre-commit.ci and whether they pass or fail. The page shows the current status and provides both Markdown and reStructured Text code for adding badges to your source documents (e.g. the Markdown badge can be added to your repositories top-level README.md and the badge will be displayed on GitHub)

-

+

Pre-commit.ci jobs pass

You can click through and see the results of a given run and when they pass they look similar to the output you would have seen when making commits locally.

-

+

Pre-commit.ci jobs pass

But sometimes things will fail as shown below where the trailing-whitespace hook failed and the file was modified. But since pre-commit.ci corrects and pushes such changes automatically you can see at the bottom that these changes were pushed to the Pull Request from which the originated.

-

+

Pre-commit.ci jobs fail

@@ -304,14 +304,14 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7,

Once you have done this your CI/CD pipeline should show at the very start the .pre stage…

-

+

GitLab pre-commit pipeline.

…and you can click through on this to see the details of the pipeline. Note that it takes a while to run as it has to download and initialise all of the environments for each configured hook unlike pre-commit.ci (this is akin to writing your own GitHub Action to run pre-commit which would also have to download and initialise the environments).

-

+

Success! GitLab pre-commit hooks pass!

@@ -352,12 +352,12 @@ No matching items author = {Neil Shephard}, title = {Pre-Commit.ci : {Integrating} {Pre-Commit} into {CI/CD}}, date = {2023-02-06}, - url = {https://ns-rse.github.io//posts/pre-commit-ci}, + url = {https://blog.nshephard.dev//posts/pre-commit-ci}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Pre-Commit.ci : Integrating Pre-Commit into -CI/CD.” February 6, 2023. https://ns-rse.github.io//posts/pre-commit-ci. +CI/CD.” February 6, 2023. https://blog.nshephard.dev//posts/pre-commit-ci.
]]>
code analysis @@ -366,14 +366,14 @@ CI/CD.” February 6, 2023.
Who’s to Blame Neil Shephard - https://ns-rse.github.io/posts/whos_to_blame/index.html + https://blog.nshephard.dev/posts/whos_to_blame/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Who’s to Blame.” December 17, 2022. -https://ns-rse.github.io//posts/whos_to_blame. +https://blog.nshephard.dev//posts/whos_to_blame.
]]> code analysis @@ -456,14 +456,14 @@ Neil Shephard. 2022. “Who’s to Blame.” December 17, 2022. github gitlab blame - https://ns-rse.github.io/posts/whos_to_blame/index.html + https://blog.nshephard.dev/posts/whos_to_blame/index.html Sat, 17 Dec 2022 00:00:00 GMT Pre-Commit : Customising and Updating Neil Shephard - https://ns-rse.github.io/posts/pre-commit-updates/index.html + https://blog.nshephard.dev/posts/pre-commit-updates/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Pre-Commit : Customising and -Updating.” November 15, 2022. https://ns-rse.github.io//posts/pre-commit-updates. +Updating.” November 15, 2022. https://blog.nshephard.dev//posts/pre-commit-updates.
]]>
code analysis @@ -589,14 +589,14 @@ Updating.” November 15, 2022.
Linux Command Line Alternatives Neil Shephard - https://ns-rse.github.io/posts/cli-alternatives/index.html + https://blog.nshephard.dev/posts/cli-alternatives/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Linux Command Line Alternatives.” -September 18, 2022. https://ns-rse.github.io//posts/cli-alternatives. +September 18, 2022. https://blog.nshephard.dev//posts/cli-alternatives.
]]> code linux bash - https://ns-rse.github.io/posts/cli-alternatives/index.html + https://blog.nshephard.dev/posts/cli-alternatives/index.html Sun, 18 Sep 2022 00:00:00 GMT Pre-Commit : Protecting your future self Neil Shephard - https://ns-rse.github.io/posts/pre-commit/index.html + https://blog.nshephard.dev/posts/pre-commit/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Pre-Commit : Protecting Your Future -Self.” August 28, 2022. https://ns-rse.github.io//posts/pre-commit. +Self.” August 28, 2022. https://blog.nshephard.dev//posts/pre-commit.
]]>
code analysis @@ -1156,14 +1156,14 @@ Self.” August 28, 2022.
Linting - What is all the fluff about? Neil Shephard - https://ns-rse.github.io/posts/linting/index.html + https://blog.nshephard.dev/posts/linting/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Linting - What Is All the Fluff -About?” August 18, 2022. https://ns-rse.github.io//posts/linting. +About?” August 18, 2022. https://blog.nshephard.dev//posts/linting.
]]> code linting python R - https://ns-rse.github.io/posts/linting/index.html + https://blog.nshephard.dev/posts/linting/index.html Thu, 18 Aug 2022 00:00:00 GMT diff --git a/about-git.xml b/about-git.xml index 7d22e70..ca0f1e7 100644 --- a/about-git.xml +++ b/about-git.xml @@ -5,21 +5,21 @@ xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"> -ns-rse -https://ns-rse.github.io/about.html#category=git - +nshephard.dev +https://blog.nshephard.dev/about.html#category=git + Software development in a Research Environment -https://ns-rse.github.io/img/profile.jpg -ns-rse -https://ns-rse.github.io/about.html#category=git +https://blog.nshephard.dev/img/profile.jpg +nshephard.dev +https://blog.nshephard.dev/about.html#category=git quarto-1.3.14 Sat, 17 Feb 2024 00:00:00 GMT Git Remotes Revisited Neil Shephard - https://ns-rse.github.io/posts/git-remotes-revisited/index.html + https://blog.nshephard.dev/posts/git-remotes-revisited/index.html I’ve written before about Git Remotes but in my on-going effort to improve my understanding of the tools I use daily I’ve discovered that it is possible to have a single remote push to two different URLs so am revisiting the topic and perhaps writing a little more clearly on it.

@@ -260,24 +260,24 @@ No matching items author = {Neil Shephard}, title = {Git {Remotes} {Revisited}}, date = {2024-02-17}, - url = {https://ns-rse.github.io//posts/git-remotes-revisited}, + url = {https://blog.nshephard.dev//posts/git-remotes-revisited}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2024. “Git Remotes Revisited.” February 17, -2024. https://ns-rse.github.io//posts/git-remotes-revisited. +2024. https://blog.nshephard.dev//posts/git-remotes-revisited.
]]>
git github gitlab - https://ns-rse.github.io/posts/git-remotes-revisited/index.html + https://blog.nshephard.dev/posts/git-remotes-revisited/index.html Sat, 17 Feb 2024 00:00:00 GMT
Git Remotes Neil Shephard - https://ns-rse.github.io/posts/git-remotes/index.html + https://blog.nshephard.dev/posts/git-remotes/index.html “Git Remotes Revisited.” February 17,

Git and various forges such as GitHub GitLab are useful collaborative tools for version controlling, sharing and working collaboratively. Normally a repository resides on your local computer and it tracks a remote (often referred to as origin)

@@ -391,23 +391,23 @@ No matching items author = {Neil Shephard}, title = {Git {Remotes}}, date = {2023-10-06}, - url = {https://ns-rse.github.io//posts/git-remotes}, + url = {https://blog.nshephard.dev//posts/git-remotes}, langid = {en} }
For attribution, please cite this work as:
-Neil Shephard. 2023. “Git Remotes.” October 6, 2023. https://ns-rse.github.io//posts/git-remotes. +Neil Shephard. 2023. “Git Remotes.” October 6, 2023. https://blog.nshephard.dev//posts/git-remotes.
]]>
git github gitlab - https://ns-rse.github.io/posts/git-remotes/index.html + https://blog.nshephard.dev/posts/git-remotes/index.html Fri, 06 Oct 2023 00:00:00 GMT
Pre-commit and R Packaging Neil Shephard - https://ns-rse.github.io/posts/pre-commit-r/index.html + https://blog.nshephard.dev/posts/pre-commit-r/index.html “Git Remotes.” October 6, 2023. Lorenz Walthert, if you find it useful consider sponsoring his work, these things take a lot of time and effort and whilst they can be used for free are worth supporting.

@@ -681,26 +681,26 @@ No matching items author = {Neil Shephard}, title = {Pre-Commit and {R} {Packaging}}, date = {2023-07-29}, - url = {https://ns-rse.github.io//posts/pre-commit-r}, + url = {https://blog.nshephard.dev//posts/pre-commit-r}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Pre-Commit and R Packaging.” July 29, -2023. https://ns-rse.github.io//posts/pre-commit-r. +2023. https://blog.nshephard.dev//posts/pre-commit-r.
]]>
quarto R git pre-commit github actions - https://ns-rse.github.io/posts/pre-commit-r/index.html + https://blog.nshephard.dev/posts/pre-commit-r/index.html Sat, 29 Jul 2023 00:00:00 GMT
Pre-Commit : Useful Hooks Neil Shephard - https://ns-rse.github.io/posts/pre-commit-hooks/index.html + https://blog.nshephard.dev/posts/pre-commit-hooks/index.html “Pre-Commit and R Packaging.” July 29,

I’m a big fan of pre-commit and have written about it before (see posts on pre-commit, pre-commit CI and pre-commit updating). This post discusses some of the hooks that I use and how to configure them.

@@ -855,12 +855,12 @@ No matching items author = {Neil Shephard}, title = {Pre-Commit : {Useful} {Hooks}}, date = {2023-05-07}, - url = {https://ns-rse.github.io//posts/pre-commit-hooks}, + url = {https://blog.nshephard.dev//posts/pre-commit-hooks}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7, -2023. https://ns-rse.github.io//posts/pre-commit-hooks. +2023. https://blog.nshephard.dev//posts/pre-commit-hooks.
]]>
code analysis @@ -869,14 +869,14 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7, github gitlab pre-commit - https://ns-rse.github.io/posts/pre-commit-hooks/index.html + https://blog.nshephard.dev/posts/pre-commit-hooks/index.html Sun, 07 May 2023 00:00:00 GMT
Pre-Commit.ci : Integrating Pre-Commit into CI/CD Neil Shephard - https://ns-rse.github.io/posts/pre-commit-ci/index.html + https://blog.nshephard.dev/posts/pre-commit-ci/index.html “Pre-Commit : Useful Hooks.” May 7,

Setup is relatively straight-forward, head to https://pre-commit.ci and sign-in with your GitHub account and grant pre-commit.ci access to your account.

-

+

Pre-commit CI

Once you have granted access you can choose which repositories pre-commit.ci has access to. It is possible to grant access to all repositories but I would recommend doing so on a per-repository basis so you know and are in control of what is happening across your repositories. If you have administration rights to organisation repositories these should be listed in the “Select repositories” pull-down menu.

-

+

Granting pre-commit.ci access to GitHub

@@ -940,28 +940,28 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7,

When logged into pre-commit.ci using your GitHub account you are presented with a page similar to the following which lists the accounts and any organisations that you have authorised pre-commit.ci to access.

-

+

Pre-commit.ci account access

You can follow the links through to view the history of jobs run by pre-commit.ci and whether they pass or fail. The page shows the current status and provides both Markdown and reStructured Text code for adding badges to your source documents (e.g. the Markdown badge can be added to your repositories top-level README.md and the badge will be displayed on GitHub)

-

+

Pre-commit.ci jobs pass

You can click through and see the results of a given run and when they pass they look similar to the output you would have seen when making commits locally.

-

+

Pre-commit.ci jobs pass

But sometimes things will fail as shown below where the trailing-whitespace hook failed and the file was modified. But since pre-commit.ci corrects and pushes such changes automatically you can see at the bottom that these changes were pushed to the Pull Request from which the originated.

-

+

Pre-commit.ci jobs fail

@@ -985,14 +985,14 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7,

Once you have done this your CI/CD pipeline should show at the very start the .pre stage…

-

+

GitLab pre-commit pipeline.

…and you can click through on this to see the details of the pipeline. Note that it takes a while to run as it has to download and initialise all of the environments for each configured hook unlike pre-commit.ci (this is akin to writing your own GitHub Action to run pre-commit which would also have to download and initialise the environments).

-

+

Success! GitLab pre-commit hooks pass!

@@ -1033,12 +1033,12 @@ No matching items author = {Neil Shephard}, title = {Pre-Commit.ci : {Integrating} {Pre-Commit} into {CI/CD}}, date = {2023-02-06}, - url = {https://ns-rse.github.io//posts/pre-commit-ci}, + url = {https://blog.nshephard.dev//posts/pre-commit-ci}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Pre-Commit.ci : Integrating Pre-Commit into -CI/CD.” February 6, 2023. https://ns-rse.github.io//posts/pre-commit-ci. +CI/CD.” February 6, 2023. https://blog.nshephard.dev//posts/pre-commit-ci.
]]>
code analysis @@ -1047,14 +1047,14 @@ CI/CD.” February 6, 2023.
Who’s to Blame Neil Shephard - https://ns-rse.github.io/posts/whos_to_blame/index.html + https://blog.nshephard.dev/posts/whos_to_blame/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Who’s to Blame.” December 17, 2022. -https://ns-rse.github.io//posts/whos_to_blame. +https://blog.nshephard.dev//posts/whos_to_blame.
]]> code analysis @@ -1137,14 +1137,14 @@ Neil Shephard. 2022. “Who’s to Blame.” December 17, 2022. github gitlab blame - https://ns-rse.github.io/posts/whos_to_blame/index.html + https://blog.nshephard.dev/posts/whos_to_blame/index.html Sat, 17 Dec 2022 00:00:00 GMT Pre-Commit : Customising and Updating Neil Shephard - https://ns-rse.github.io/posts/pre-commit-updates/index.html + https://blog.nshephard.dev/posts/pre-commit-updates/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Pre-Commit : Customising and -Updating.” November 15, 2022. https://ns-rse.github.io//posts/pre-commit-updates. +Updating.” November 15, 2022. https://blog.nshephard.dev//posts/pre-commit-updates.
]]>
code analysis @@ -1270,14 +1270,14 @@ Updating.” November 15, 2022.
Pre-Commit : Protecting your future self Neil Shephard - https://ns-rse.github.io/posts/pre-commit/index.html + https://blog.nshephard.dev/posts/pre-commit/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Pre-Commit : Protecting Your Future -Self.” August 28, 2022. https://ns-rse.github.io//posts/pre-commit. +Self.” August 28, 2022. https://blog.nshephard.dev//posts/pre-commit.
]]> code analysis @@ -1454,14 +1454,14 @@ Self.” August 28, 2022. Git : Custom SSH credentials for git repositories Neil Shephard - https://ns-rse.github.io/posts/git-ssh/index.html + https://blog.nshephard.dev/posts/git-ssh/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Git : Custom SSH Credentials for Git -Repositories.” August 28, 2022. https://ns-rse.github.io//posts/git-ssh. +Repositories.” August 28, 2022. https://blog.nshephard.dev//posts/git-ssh.
]]> ssh git github gitlab keychain - https://ns-rse.github.io/posts/git-ssh/index.html + https://blog.nshephard.dev/posts/git-ssh/index.html Sun, 28 Aug 2022 00:00:00 GMT diff --git a/about-github.xml b/about-github.xml index 63446f3..0d20cbe 100644 --- a/about-github.xml +++ b/about-github.xml @@ -5,21 +5,21 @@ xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"> -ns-rse -https://ns-rse.github.io/about.html#category=github - +nshephard.dev +https://blog.nshephard.dev/about.html#category=github + Software development in a Research Environment -https://ns-rse.github.io/img/profile.jpg -ns-rse -https://ns-rse.github.io/about.html#category=github +https://blog.nshephard.dev/img/profile.jpg +nshephard.dev +https://blog.nshephard.dev/about.html#category=github quarto-1.3.14 Sat, 17 Feb 2024 00:00:00 GMT Git Remotes Revisited Neil Shephard - https://ns-rse.github.io/posts/git-remotes-revisited/index.html + https://blog.nshephard.dev/posts/git-remotes-revisited/index.html I’ve written before about Git Remotes but in my on-going effort to improve my understanding of the tools I use daily I’ve discovered that it is possible to have a single remote push to two different URLs so am revisiting the topic and perhaps writing a little more clearly on it.

@@ -260,24 +260,24 @@ No matching items author = {Neil Shephard}, title = {Git {Remotes} {Revisited}}, date = {2024-02-17}, - url = {https://ns-rse.github.io//posts/git-remotes-revisited}, + url = {https://blog.nshephard.dev//posts/git-remotes-revisited}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2024. “Git Remotes Revisited.” February 17, -2024. https://ns-rse.github.io//posts/git-remotes-revisited. +2024. https://blog.nshephard.dev//posts/git-remotes-revisited.
]]>
git github gitlab - https://ns-rse.github.io/posts/git-remotes-revisited/index.html + https://blog.nshephard.dev/posts/git-remotes-revisited/index.html Sat, 17 Feb 2024 00:00:00 GMT
Git Remotes Neil Shephard - https://ns-rse.github.io/posts/git-remotes/index.html + https://blog.nshephard.dev/posts/git-remotes/index.html “Git Remotes Revisited.” February 17,

Git and various forges such as GitHub GitLab are useful collaborative tools for version controlling, sharing and working collaboratively. Normally a repository resides on your local computer and it tracks a remote (often referred to as origin)

@@ -391,23 +391,23 @@ No matching items author = {Neil Shephard}, title = {Git {Remotes}}, date = {2023-10-06}, - url = {https://ns-rse.github.io//posts/git-remotes}, + url = {https://blog.nshephard.dev//posts/git-remotes}, langid = {en} }
For attribution, please cite this work as:
-Neil Shephard. 2023. “Git Remotes.” October 6, 2023. https://ns-rse.github.io//posts/git-remotes. +Neil Shephard. 2023. “Git Remotes.” October 6, 2023. https://blog.nshephard.dev//posts/git-remotes.
]]>
git github gitlab - https://ns-rse.github.io/posts/git-remotes/index.html + https://blog.nshephard.dev/posts/git-remotes/index.html Fri, 06 Oct 2023 00:00:00 GMT
Pre-Commit : Useful Hooks Neil Shephard - https://ns-rse.github.io/posts/pre-commit-hooks/index.html + https://blog.nshephard.dev/posts/pre-commit-hooks/index.html “Git Remotes.” October 6, 2023. pre-commit and have written about it before (see posts on pre-commit, pre-commit CI and pre-commit updating). This post discusses some of the hooks that I use and how to configure them.

@@ -562,12 +562,12 @@ No matching items author = {Neil Shephard}, title = {Pre-Commit : {Useful} {Hooks}}, date = {2023-05-07}, - url = {https://ns-rse.github.io//posts/pre-commit-hooks}, + url = {https://blog.nshephard.dev//posts/pre-commit-hooks}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7, -2023. https://ns-rse.github.io//posts/pre-commit-hooks. +2023. https://blog.nshephard.dev//posts/pre-commit-hooks.
]]>
code analysis @@ -576,14 +576,14 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7, github gitlab pre-commit - https://ns-rse.github.io/posts/pre-commit-hooks/index.html + https://blog.nshephard.dev/posts/pre-commit-hooks/index.html Sun, 07 May 2023 00:00:00 GMT
Pre-Commit.ci : Integrating Pre-Commit into CI/CD Neil Shephard - https://ns-rse.github.io/posts/pre-commit-ci/index.html + https://blog.nshephard.dev/posts/pre-commit-ci/index.html “Pre-Commit : Useful Hooks.” May 7,

Setup is relatively straight-forward, head to https://pre-commit.ci and sign-in with your GitHub account and grant pre-commit.ci access to your account.

-

+

Pre-commit CI

Once you have granted access you can choose which repositories pre-commit.ci has access to. It is possible to grant access to all repositories but I would recommend doing so on a per-repository basis so you know and are in control of what is happening across your repositories. If you have administration rights to organisation repositories these should be listed in the “Select repositories” pull-down menu.

-

+

Granting pre-commit.ci access to GitHub

@@ -647,28 +647,28 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7,

When logged into pre-commit.ci using your GitHub account you are presented with a page similar to the following which lists the accounts and any organisations that you have authorised pre-commit.ci to access.

-

+

Pre-commit.ci account access

You can follow the links through to view the history of jobs run by pre-commit.ci and whether they pass or fail. The page shows the current status and provides both Markdown and reStructured Text code for adding badges to your source documents (e.g. the Markdown badge can be added to your repositories top-level README.md and the badge will be displayed on GitHub)

-

+

Pre-commit.ci jobs pass

You can click through and see the results of a given run and when they pass they look similar to the output you would have seen when making commits locally.

-

+

Pre-commit.ci jobs pass

But sometimes things will fail as shown below where the trailing-whitespace hook failed and the file was modified. But since pre-commit.ci corrects and pushes such changes automatically you can see at the bottom that these changes were pushed to the Pull Request from which the originated.

-

+

Pre-commit.ci jobs fail

@@ -692,14 +692,14 @@ Neil Shephard. 2023. “Pre-Commit : Useful Hooks.” May 7,

Once you have done this your CI/CD pipeline should show at the very start the .pre stage…

-

+

GitLab pre-commit pipeline.

…and you can click through on this to see the details of the pipeline. Note that it takes a while to run as it has to download and initialise all of the environments for each configured hook unlike pre-commit.ci (this is akin to writing your own GitHub Action to run pre-commit which would also have to download and initialise the environments).

-

+

Success! GitLab pre-commit hooks pass!

@@ -740,12 +740,12 @@ No matching items author = {Neil Shephard}, title = {Pre-Commit.ci : {Integrating} {Pre-Commit} into {CI/CD}}, date = {2023-02-06}, - url = {https://ns-rse.github.io//posts/pre-commit-ci}, + url = {https://blog.nshephard.dev//posts/pre-commit-ci}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Pre-Commit.ci : Integrating Pre-Commit into -CI/CD.” February 6, 2023. https://ns-rse.github.io//posts/pre-commit-ci. +CI/CD.” February 6, 2023. https://blog.nshephard.dev//posts/pre-commit-ci.
]]>
code analysis @@ -754,14 +754,14 @@ CI/CD.” February 6, 2023.
Who’s to Blame Neil Shephard - https://ns-rse.github.io/posts/whos_to_blame/index.html + https://blog.nshephard.dev/posts/whos_to_blame/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Who’s to Blame.” December 17, 2022. -https://ns-rse.github.io//posts/whos_to_blame. +https://blog.nshephard.dev//posts/whos_to_blame.
]]> code analysis @@ -844,14 +844,14 @@ Neil Shephard. 2022. “Who’s to Blame.” December 17, 2022. github gitlab blame - https://ns-rse.github.io/posts/whos_to_blame/index.html + https://blog.nshephard.dev/posts/whos_to_blame/index.html Sat, 17 Dec 2022 00:00:00 GMT Pre-Commit : Customising and Updating Neil Shephard - https://ns-rse.github.io/posts/pre-commit-updates/index.html + https://blog.nshephard.dev/posts/pre-commit-updates/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Pre-Commit : Customising and -Updating.” November 15, 2022. https://ns-rse.github.io//posts/pre-commit-updates. +Updating.” November 15, 2022. https://blog.nshephard.dev//posts/pre-commit-updates.
]]>
code analysis @@ -977,14 +977,14 @@ Updating.” November 15, 2022.
Pre-Commit : Protecting your future self Neil Shephard - https://ns-rse.github.io/posts/pre-commit/index.html + https://blog.nshephard.dev/posts/pre-commit/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Pre-Commit : Protecting Your Future -Self.” August 28, 2022. https://ns-rse.github.io//posts/pre-commit. +Self.” August 28, 2022. https://blog.nshephard.dev//posts/pre-commit.
]]> code analysis @@ -1161,14 +1161,14 @@ Self.” August 28, 2022. Git : Custom SSH credentials for git repositories Neil Shephard - https://ns-rse.github.io/posts/git-ssh/index.html + https://blog.nshephard.dev/posts/git-ssh/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Git : Custom SSH Credentials for Git -Repositories.” August 28, 2022. https://ns-rse.github.io//posts/git-ssh. +Repositories.” August 28, 2022. https://blog.nshephard.dev//posts/git-ssh.
]]> ssh git github gitlab keychain - https://ns-rse.github.io/posts/git-ssh/index.html + https://blog.nshephard.dev/posts/git-ssh/index.html Sun, 28 Aug 2022 00:00:00 GMT diff --git a/about-python.xml b/about-python.xml index b950b3c..8f03d66 100644 --- a/about-python.xml +++ b/about-python.xml @@ -5,21 +5,21 @@ xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"> -ns-rse -https://ns-rse.github.io/about.html#category=python - +nshephard.dev +https://blog.nshephard.dev/about.html#category=python + Software development in a Research Environment -https://ns-rse.github.io/img/profile.jpg -ns-rse -https://ns-rse.github.io/about.html#category=python +https://blog.nshephard.dev/img/profile.jpg +nshephard.dev +https://blog.nshephard.dev/about.html#category=python quarto-1.3.14 Mon, 01 Jan 2024 00:00:00 GMT Pytest Parameterisation Neil Shephard - https://ns-rse.github.io/posts/pytest-param/index.html + https://blog.nshephard.dev/posts/pytest-param/index.html Pytest is an excellent framework for writing tests in Python. One of the neat features it includes is the ability to parameterise your tests which means you can write one test and pass different sets of parameters into it to test the range of actions that the function/method are meant to handle.

@@ -339,24 +339,24 @@ No matching items author = {Neil Shephard}, title = {Pytest {Parameterisation}}, date = {2024-01-01}, - url = {https://ns-rse.github.io//posts/pytest-param}, + url = {https://blog.nshephard.dev//posts/pytest-param}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2024. “Pytest Parameterisation.” January 1, -2024. https://ns-rse.github.io//posts/pytest-param. +2024. https://blog.nshephard.dev//posts/pytest-param.
]]>
python testing pytest - https://ns-rse.github.io/posts/pytest-param/index.html + https://blog.nshephard.dev/posts/pytest-param/index.html Mon, 01 Jan 2024 00:00:00 GMT
virtualenvwrapper Neil Shephard - https://ns-rse.github.io/posts/virtualenvwrapper/index.html + https://blog.nshephard.dev/posts/virtualenvwrapper/index.html “Pytest Parameterisation.” January 1,

If you use Python heavily you will likely be familiar with Virtual Environments. These provide isolated installs of specific packages that take precedence over any packages installed at the system level. There are lots of tools and frameworks for working with virtual environments such as venv, virtualenv and Conda. This post introduces and shows some of the features of virtualenvwrapper.

@@ -458,23 +458,23 @@ No matching items author = {Neil Shephard}, title = {Virtualenvwrapper}, date = {2023-12-23}, - url = {https://ns-rse.github.io//posts/virtualenvwrapper}, + url = {https://blog.nshephard.dev//posts/virtualenvwrapper}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Virtualenvwrapper.” December 23, -2023. https://ns-rse.github.io//posts/virtualenvwrapper. +2023. https://blog.nshephard.dev//posts/virtualenvwrapper.
]]>
python virtual environments - https://ns-rse.github.io/posts/virtualenvwrapper/index.html + https://blog.nshephard.dev/posts/virtualenvwrapper/index.html Sat, 23 Dec 2023 00:00:00 GMT
Repository Review with Scientific Python Neil Shephard - https://ns-rse.github.io/posts/repository-review/index.html + https://blog.nshephard.dev/posts/repository-review/index.html “Virtualenvwrapper.” December 23,

I’ve written before about Python Packaging and pre-commit which I’m a big fan of. Today I discovered a really useful tool for checking your packaging configuration and pre-commit configuration from the Scientific Python Development Guide.

-

+

Elektro

@@ -523,25 +523,25 @@ No matching items author = {Neil Shephard}, title = {Repository {Review} with {Scientific} {Python}}, date = {2023-11-17}, - url = {https://ns-rse.github.io//posts/repository-review}, + url = {https://blog.nshephard.dev//posts/repository-review}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Repository Review with Scientific -Python.” November 17, 2023. https://ns-rse.github.io//posts/repository-review. +Python.” November 17, 2023. https://blog.nshephard.dev//posts/repository-review.
]]>
pre-commit packaging scientific python python - https://ns-rse.github.io/posts/repository-review/index.html + https://blog.nshephard.dev/posts/repository-review/index.html Fri, 17 Nov 2023 00:00:00 GMT
GitLab CI - Automatic Publishing to PyPI Neil Shephard - https://ns-rse.github.io/posts/gitlab-ci-pypi/index.html + https://blog.nshephard.dev/posts/gitlab-ci-pypi/index.html November 17, 2023. Python Packaging and in that article included details of how to automate publishing to PyPI from GitHub. This article details how to automatically publish your package to PyPI from GitLab.

@@ -733,26 +733,26 @@ No matching items author = {Neil Shephard}, title = {GitLab {CI} - {Automatic} {Publishing} to {PyPI}}, date = {2023-10-03}, - url = {https://ns-rse.github.io//posts/gitlab-ci-pypi}, + url = {https://blog.nshephard.dev//posts/gitlab-ci-pypi}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “GitLab CI - Automatic Publishing to -PyPI.” October 3, 2023. https://ns-rse.github.io//posts/gitlab-ci-pypi. +PyPI.” October 3, 2023. https://blog.nshephard.dev//posts/gitlab-ci-pypi.
]]>
python documentation packaging gitlab ci - https://ns-rse.github.io/posts/gitlab-ci-pypi/index.html + https://blog.nshephard.dev/posts/gitlab-ci-pypi/index.html Tue, 03 Oct 2023 00:00:00 GMT
Sphinx Documentation Neil Shephard - https://ns-rse.github.io/posts/sphinx-docs/index.html + https://blog.nshephard.dev/posts/sphinx-docs/index.html October 3, 2023. Sphinx, including generating API documentation automatically, build multiple versions across releases and automatically build and host them on GitHub Pages.

@@ -1081,26 +1081,26 @@ No matching items author = {Neil Shephard}, title = {Sphinx {Documentation}}, date = {2023-05-07}, - url = {https://ns-rse.github.io//posts/sphinx-docs}, + url = {https://blog.nshephard.dev//posts/sphinx-docs}, langid = {en} }
For attribution, please cite this work as:
Neil Shephard. 2023. “Sphinx Documentation.” May 7, 2023. -https://ns-rse.github.io//posts/sphinx-docs. +https://blog.nshephard.dev//posts/sphinx-docs.
]]>
quarto python documentation sphinx github actions - https://ns-rse.github.io/posts/sphinx-docs/index.html + https://blog.nshephard.dev/posts/sphinx-docs/index.html Sun, 07 May 2023 00:00:00 GMT
Python Packaging Neil Shephard - https://ns-rse.github.io/posts/python-packaging/index.html + https://blog.nshephard.dev/posts/python-packaging/index.html “Sphinx Documentation.” May 7, 2023.

This post describes steps in creating a Python package. If you are looking for information on installing packages this is done using Python PIP.

@@ -1477,11 +1477,11 @@ No matching items author = {Neil Shephard}, title = {Python {Packaging}}, date = {2023-03-25}, - url = {https://ns-rse.github.io//posts/python-packaging}, + url = {https://blog.nshephard.dev//posts/python-packaging}, langid = {en} }
For attribution, please cite this work as:
-Neil Shephard. 2023. “Python Packaging.” March 25, 2023. https://ns-rse.github.io//posts/python-packaging. +Neil Shephard. 2023. “Python Packaging.” March 25, 2023. https://blog.nshephard.dev//posts/python-packaging.
]]>
quarto python @@ -1489,14 +1489,14 @@ Neil Shephard. 2023. “Python Packaging.” March 25, 2023. setuptools github actions pypi - https://ns-rse.github.io/posts/python-packaging/index.html + https://blog.nshephard.dev/posts/python-packaging/index.html Sat, 25 Mar 2023 00:00:00 GMT
Linting - What is all the fluff about? Neil Shephard - https://ns-rse.github.io/posts/linting/index.html + https://blog.nshephard.dev/posts/linting/index.html
For attribution, please cite this work as:
Neil Shephard. 2022. “Linting - What Is All the Fluff -About?” August 18, 2022. https://ns-rse.github.io//posts/linting. +About?” August 18, 2022. https://blog.nshephard.dev//posts/linting.
]]> code linting python R - https://ns-rse.github.io/posts/linting/index.html + https://blog.nshephard.dev/posts/linting/index.html Thu, 18 Aug 2022 00:00:00 GMT diff --git a/about.html b/about.html index 47bb5f7..d8aedea 100644 --- a/about.html +++ b/about.html @@ -8,7 +8,7 @@ -ns-rse - About +nshephard.dev - About