Auto merge of #9097 - ehuss:tracking-issue-template-update, r=alexcrichton

Minor update to tracking issue template.

Just some minor tweaks, move the "about" to the bottom since it isn't that important (I think the summary should be first). Also add a link to an RFC if it is an RFC.

Author: bors

.github/ISSUE_TEMPLATE/tracking_issue.md

@@ -10,15 +10,9 @@ accepted feature or RFC from implementation to stabilization. Please do not
 file a tracking issue until the feature or RFC has been approved.
 -->
 
-**About tracking issues**
-
-Tracking issues are used to record the overall progress of implementation.
-They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
-A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
-Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
-
 **Summary**
 
+RFC: [#NNNN](https://github.com/rust-lang/rfcs/pull/NNNN) <!-- If this is an RFC -->
 Original issue: #NNNN <!-- if there is a related issue that spawned this feature -->
 Implementation: #NNNN <!-- link to the PR that implemented this feature if applicable -->
 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#my-feature
@@ -32,3 +26,10 @@ Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#m
 **Future extensions**
 
 <!-- An optional section where you can mention where the feature may be extended in the future, but is explicitly not intended to address. -->
+
+**About tracking issues**
+
+Tracking issues are used to record the overall progress of implementation.
+They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
+A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
+Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.