Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

XS✔ ◾ removed absolute urls #7590

Merged
merged 2 commits into from
Dec 17, 2023
Merged

XS✔ ◾ removed absolute urls #7590

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
149230b
removed absolute urls
BrookJeynes Dec 17, 2023
4e5ffd8
Auto-fix Markdown files
github-actions[bot] Dec 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion rules/do-you-use-co-creation-patterns/rule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Inefficient code reviews can be caused by:
* This requires a smaller block of time to review which makes it easier for the reviewer to find the time
* Less risk - reduces the chance of an incorrect approach being taken
* Get quality feedback - small blocks of code are easier to digest
* Create a [great pull request](https://www.ssw.com.au/rules/write-a-good-pull-request/) to make it easier for the reviewer to understand your changes.
* Create a [great pull request](/write-a-good-pull-request/) to make it easier for the reviewer to understand your changes.
* Reviewer - When reviewing asynchronously
* Be explicit and suggest the exact code changes where possible (GitHub has a feature for this, see <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request>)
* Call the developer for more complicated changes
Expand Down
8 changes: 4 additions & 4 deletions rules/do-you-zz-old-files-rather-than-deleting-them/rule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ created: 2009-03-02T02:45:33.000Z
archivedreason: null
guid: 89900a3a-2e3d-4d72-b935-0949bd1cd8ed
---
When you are regularly creating new releases of a cool .NET application or simply producing new proposals in Microsoft Word, files will inevitably become **outdated**. Rather than deleting them, put a 'zz' at the front of the filename. These old versions should not be deleted straight away - it is just an unnecessary risk! The zz'd files can remain there until you need more space, then you should delete them.
When you are regularly creating new releases of a cool .NET application or simply producing new proposals in Microsoft Word, files will inevitably become **outdated**. Rather than deleting them, put a 'zz' at the front of the filename. These old versions should not be deleted straight away - it is just an unnecessary risk! The zz'd files can remain there until you need more space, then you should delete them.

<!--endintro-->

Expand All @@ -44,7 +44,7 @@ Both allow for some backward compatibility.

When uploading to some video hosting sites, like Vimeo, you can update a video by replacing the original video while keeping the same URL and view count.

In YouTube an uploaded video can't be replaced, so to create a new version of a video it will be uploaded as a new video with a new URL.
In YouTube an uploaded video can't be replaced, so to create a new version of a video it will be uploaded as a new video with a new URL.

So that there are no broken or missing links, the video status is set to "unlisted", and we use the 'zz' process:

Expand All @@ -65,6 +65,6 @@ On YouTube click the ‘New Version’ link in the description.

::: info

If you are deleting something that uses resources and/or cost money, it is a good idea to 'zz' it first - and use a follow up to remind yourself to delete it after a reasonable amount of time, as per: https://www.ssw.com.au/rules/follow-up-effectively/
If you are deleting something that uses resources and/or cost money, it is a good idea to 'zz' it first - and use a follow up to remind yourself to delete it after a reasonable amount of time, as per: [https://www.ssw.com.au/rules/follow-up-effectively/](/follow-up-effectively/)

:::
:::