From 43ef7c2c7020efcd4d24a0ca7f10614f0ef43234 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Fri, 14 Oct 2022 23:54:41 +0100 Subject: [PATCH] docs(daily-emails): add 2022-10-10 --- website/src/daily-emails/2022-10-10.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 website/src/daily-emails/2022-10-10.md diff --git a/website/src/daily-emails/2022-10-10.md b/website/src/daily-emails/2022-10-10.md new file mode 100644 index 00000000..ff35bb15 --- /dev/null +++ b/website/src/daily-emails/2022-10-10.md @@ -0,0 +1,14 @@ +--- +title: Contributing to open-source software, one small change at a time +pubDate: "2022-10-10" +permalink: archive/2022/10/10/contributing-open-source-software-one-small-change-time +tags: [open-source] +--- + +Since looking more into Astro, I was looking through the GitHub repository - specifically within the examples - and spotted a typo within the title of one of the examples. + +Rather than leaving it, I decided to follow the "boy-scout rule" and submit a fix and leave the code in a better state than I found it. + +The Astro repository is hosted on GitHub so I was able to fork the repository, fix the typo and create a pull request with a few clicks in the GitHub UI. + +Contributing to open-source software - particularly if you're new to it - doesn't mean that you need to always add large and complex changes. Small changes such as fixing a typo, updating documentation, fixing a small bug, or adding additional tests are all valid contributions that improve open-source projects.