Add freeze & restriction warning (#265)

I believe this is slipped over many people and end up spending time
making something that is under a freeze/not preparing a design doc
before spending their time.

This may help a bit

src/en/general-development/setup/git-for-the-ss14-developer.md

@@ -202,6 +202,10 @@ The convention is to call the remote pointing to the original repository `upstre
 
 **Addendum for fork/downstream developers:** If a downstream repository you wish to contribute to is set up as a direct fork (IE: GitHub shows a "forked from" label underneath the repo's name), then you'll additionally want to add that fork as a remote (but if the fork isn't set up that way, you can ignore this). You can do this in a way similar to how you've added the upstream as a remote (just use the fork's GitHub link as the remote URL), but be sure to substitute the remote name of `upstream` with any name you deem appropriate. Your own fork does not have to be a fork of the downstream's fork for this; all that matters is that the commit history in the individual branches you push to your own remote line up with the commit history of wherever you're intending to PR your changes to.
 
+```admonish warning title="Before working on your first PR to the space-wizards repo"
+Please make sure you read through the [Freezes & Restrictions](https://github.com/space-wizards/space-station-14/issues/8524) and ensure your idea does not fall into the freezes or if your PR requires some prerequisite before being made. 
+```
+
 ## 4. Branching & Commits
 
 Branches and commits are two of the most important concepts in Git, and most of the work you do will revolve around them.