chore: update docs from development branch

.github/ISSUE_TEMPLATE/bug_report_or_issue.md

@@ -11,7 +11,7 @@ assignees: ''
 
 * Python Version:
 * Operating System:
-* Target System Type: (_e.g. Dell, SuperMicro_)
+* Target System Type: (_e.g. Dell, Supermicro_)
 * IPMI / Out-of-band Firmware Version: (_e.g. iDRAC 8 2.60.60.60)
 
 **Describe the bug**

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -8,7 +8,7 @@
 ### New Feature Submissions:
 
 1. [ ] Does your submission pass tests?
-2. [ ] Have you lint your code locally before submission?
+2. [ ] Have you linted your code locally before submission?
 
 ### Changes to Core Features:
 

.github/workflows/production-release.yml

@@ -136,10 +136,11 @@ jobs:
             - name: Build and Push
               run: |
                   # Added --no-cache to ensure fresh layers
-                  podman build --no-cache -t quay.io/quads/badfish:master .
+                  # Retry pulls/pushes to ride out transient Quay CDN EOFs
+                  podman build --no-cache --retry=5 --retry-delay=15s -t quay.io/quads/badfish:master .
                   podman tag quay.io/quads/badfish:master quay.io/quads/badfish:latest
-                  podman push quay.io/quads/badfish:master
-                  podman push quay.io/quads/badfish:latest
+                  podman push --retry=5 --retry-delay=15s quay.io/quads/badfish:master
+                  podman push --retry=5 --retry-delay=15s quay.io/quads/badfish:latest
 
     # ------------------------------------------------------------------
     # JOB 4: AUR PUBLISH

CONTRIBUTING.md

@@ -13,14 +13,14 @@ To get an overview of the project, read the [README](README.md). Here are some r
 - [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
 - [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git)
 - [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow)
-- [Collaborating with pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests)
+- [Collaborating with pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests)
 
 
 ## Getting started
 
 We love pull requests and welcome contributions from everyone!  Please use the `development` branch to send pull requests.  Here are the general steps you'd want to follow.
 
-1. Fork the Badfish Github repository
+1. Fork the Badfish GitHub repository
 2. Clone the forked repository
 3. Push your changes to your forked clone
 4. Open a pull request against our `development` branch.
@@ -29,7 +29,7 @@ We love pull requests and welcome contributions from everyone!  Please use the `
 
 #### Create a new issue
 
-If you spot a problem with badfish, [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments). If a related issue doesn't exist, you can open a new issue using a relevant [issue form](https://github.com/quadsproject/badfish/issues/new/choose).
+If you spot a problem with badfish, [search if an issue already exists](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments). If a related issue doesn't exist, you can open a new issue using a relevant [issue form](https://github.com/quadsproject/badfish/issues/new/choose).
 
 #### Solve an issue
 
@@ -41,10 +41,10 @@ Scan through our [existing issues](https://github.com/quadsproject/badfish/issue
 
 1. Fork the repository.
 - Using the command line:
-  - [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them.
+  - [Fork the repo](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them.
 
 - GitHub Codespaces:
-  - [Fork, edit, and preview](https://docs.github.com/en/free-pro-team@latest/github/developing-online-with-codespaces/creating-a-codespace) using [GitHub Codespaces](https://github.com/features/codespaces) without having to install and run the project locally.
+  - [Fork, edit, and preview](https://docs.github.com/en/codespaces/quickstart) using [GitHub Codespaces](https://github.com/features/codespaces) without having to install and run the project locally.
 
 2. Create a working branch and start with your changes!
 
@@ -55,12 +55,12 @@ Commit the changes once you are happy with them. See [Atom's contributing guide]
 ### Pull Request
 
 When you're finished with the changes, create a pull request, also known as a PR.
-- Fill the "Ready for review" template so that we can review your PR. This template helps reviewers understand your changes as well as the purpose of your pull request.
+- Fill in the pull request template so that we can review your PR. This template helps reviewers understand your changes as well as the purpose of your pull request.
 - Don't forget to [link PR to issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if you are solving one.
-- Enable the checkbox to [allow maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge.
-Once you submit your PR, a Docs team member will review your proposal. We may ask questions or request for additional information.
-- We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
-- As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations).
+- Enable the checkbox to [allow maintainer edits](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge.
+Once you submit your PR, a Badfish team member will review your proposal. We may ask questions or request additional information.
+- We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
+- As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#resolving-conversations).
 - If you run into any merge issues, checkout this [git tutorial](https://lab.github.com/githubtraining/managing-merge-conflicts) to help you resolve merge conflicts and other issues.
 
 ### Your PR is merged!