new repo URL

Author: GreemDev

CHANGELOG.md

@@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - Fixed duplicate key error in `GitRepository.GetRemoteNameAndBranch`
     - Instead, only the most recent value is retained.
 - Refactored the documentation in-repository to work on `mkdocs`:
-  - https://github.com/GreemDev/NUKE-Docs
+  - https://github.com/gruke-build/docs
   - View the deployment on [gruke.readthedocs.io](https://gruke.readthedocs.io).
 - Added support for XML Solutions into `gruke :setup` ([nuke-build#1572](https://github.com/nuke-build/nuke/pull/1572))
   - Thanks, [@lahma](https://github.com/lahma)!

CONTRIBUTING.md

@@ -4,7 +4,11 @@ As a community, we want to help each other, provide constructive feedback, and m
 
 ## Consumer Expectations
 
-NUKE is a personal project that was made open-source to let the whole community benefit from it **free of charge** but also ["as is"](https://github.com/GreemDev/NUKE/blob/develop/LICENSE). Like many open-source projects, it is primarily maintained and developed by a [single person](https://github.com/matkoch). Some of the **most time-consuming tasks** around the project are:
+NUKE is a personal project that was made open-source to let the whole community benefit from it **free of charge** but also ["as is"](https://github.com/gruke-build/src/blob/develop/LICENSE). 
+Like many open-source projects, it is primarily maintained and developed by a [single person](https://github.com/GreemDev). 
+This is a fork of [NUKE](https://nuke.build), originally maintained and developed by [matkoch](https://github.com/matkoch).
+
+Some of the **most time-consuming tasks** around the project are:
 
 - Development of the NuGet package itself (C#, .NET, MSBuild)
 - Collecting CLI metadata (.NET ClI, MSBuild, Docker, +30 others)
@@ -25,9 +29,8 @@ Therefore, **everything that benefits a larger audience is prioritized** over di
 
 There are several minimal to zero efforts you can make to show your support for the project:
 
-- Give the [GitHub project](https://github.com/nuke-build/nuke/stargazers) a star (and tell your team)
-- Upvote, share and comment on our content (see [#mentions](https://app.slack.com/client/T9QUKHC4A/CDJD8CGQ5) on Slack)
-- Talk about NUKE on social media and let others know where it can help (tag us!)
+- Give the [GitHub project](https://github.com/gruke-build/src/stargazers) a star (and tell your team)
+- Talk about NUKE on social media and let others know where it can help
 
 The above points are considered somewhat of the norm in exchange for using the project free of charge.
 
@@ -51,16 +54,16 @@ Evaluate whether your topic is going to be a valid issue:
 
 - Have you read and searched the [documentation](https://gruke.readthedocs.io/en/latest/introduction/)?
 - Have you checked the [FAQ](https://nuke.build/faq/)?
-- Is your issue more of a question? Ask on [GitHub discussions](https://github.com/GreemDev/NUKE/discussions)!
+- Is your issue more of a question? Ask on [GitHub discussions](https://github.com/gruke-build/src/discussions)!
 - Have you checked existing/closed issues? Is your version behind?
-- Have you read the relevant [changelog notes](https://github.com/GreemDev/NUKE/blob/develop/CHANGELOG.md)?
+- Have you read the relevant [changelog notes](https://github.com/gruke-build/src/blob/develop/CHANGELOG.md)?
 - Have you verified it's not an external tool issue? Invoke the command manually!
 - Don't file issues for tool wrappers. Send a pull request instead!
 - Refrain from debating the governance or state of the project out of your own interests (see [consumer expectations](#consumer-expectations) & [sustainability contributions](#sustainability-contributions))
 
 ### When creating an issue
 
-Choose one of the [issue templates](https://github.com/GreemDev/NUKE/issues/new/choose) and fill it out as well as possible. This includes, but is not limited to:
+Choose one of the [issue templates](https://github.com/gruke-build/src/issues/new/choose) and fill it out as well as possible. This includes, but is not limited to:
 
 - State the issue as short as possible (more likely there's time to comprehend it)
 - Use [markdown](https://docs.github.com/en/get-started/writing-on-github) for code, logs, and other special text fragments
@@ -86,7 +89,7 @@ The issue will be addressed sooner or later depending on the priority, available
 
 In your own interest of getting a pull-request merged (timely):
 
-- Discuss non-trivial changes in an [issue](https://github.com/GreemDev/NUKE/issues/new/choose)
+- Discuss non-trivial changes in an [issue](https://github.com/gruke-build/src/issues/new/choose)
 - Make sure your employer allows contributions
 - Branch your work off from the `develop` branch
 - Get familiar with the coding conventions
@@ -105,7 +108,7 @@ In your own interest of getting a pull-request merged (timely):
 - [Link the issue it relates to](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) (unless it's trivial)
 - Check all the applicable boxes
 
-For tool wrappers (e.g. [.NET CLI](https://github.com/GreemDev/NUKE/blob/develop/source/Nuke.Common/Tools/DotNet/DotNet.json)), also note the following remarks:
+For tool wrappers (e.g. [.NET CLI](https://github.com/gruke-build/src/blob/develop/source/Nuke.Common/Tools/DotNet/DotNet.json)), also note the following remarks:
 
 - Copy/paste as much as possible
 - Cover at least a full command with all its arguments