[backport] ruamel refactor 7.x.x

.github/CODEOWNERS

@@ -2,16 +2,15 @@
 
 # Universal RP General
 /com.unity.render-pipelines.universal/ @Unity-Technologies/universal-rp-team
-/com.unity.render-pipelines.universal/CHANGELOG.md @Unity-Technologies/gfx-docs
 
 # Universal RP 2D Renderer
 /com.unity.render-pipelines.universal/Editor/2D @Unity-Technologies/2d-graphics
 /com.unity.render-pipelines.universal/Runtime/2D @Unity-Technologies/2d-graphics
 /com.unity.render-pipelines.universal/Shaders/2D @Unity-Technologies/2d-graphics
 /com.unity.render-pipelines.universal/Editor/ShaderGraph/MasterNodes @Unity-Technologies/2d-graphics
 
-# Shadergraph
-/com.unity.shadergraph/CHANGELOG.md @Unity-Technologies/gfx-docs
+# Shader Graph
+/com.unity.shadergraph/ @Unity-Technologies/shader-graph @Unity-Technologies/gfx-qa-bellevue
 
 # Test systems
 /.yamato/ @Unity-Technologies/gfx-sdets
@@ -20,4 +19,3 @@
 
 # LWRP (Legacy)
 /com.unity.render-pipelines.lightweight/ @Unity-Technologies/universal-rp-team
-/com.unity.render-pipelines.lightweight/CHANGELOG.md @Unity-Technologies/gfx-docs

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,30 +1,37 @@
-### Purpose of this PR
-Why is this PR needed, what hard problem is it solving/fixing?
+### **Please read**
+**PR workflow guidelines**
+* SRP ABV will start automatically when you open your PR
+* Changes to docs and md files will **not** trigger ABV jobs 
+* Consider making use of **draft PRs** if you are not 100% sure that your PR is ready for review
+* ABV will restart if you add a new commit to a branch with an open PR (hence why you should consider using draft PRs)
+* Adding [skip ci] (case insensitive) to the title of PRs will stop any jobs being trigger automatically - you will need to open Yamato and find your branch to run ABV
+
+### Checklist for PR maker
+- [ ] Have you added a backport label (if needed)? For example, the `need-backport-2019.3` label. After you backport the PR, the label changes to `backported-2019.3`.
+- [ ] Have you updated the changelog? Each package has a `CHANGELOG.md` file.
+- [ ] Have you updated or added the documentation for your PR? When you add a new feature, change a property name, or change the behavior of a feature, it's best practice to include related documentation changes in the same PR.
+- [ ] Have you added a graphic test for your PR (if needed)? When you add a new feature, or discover a bug that tests don't cover, please add a graphic test.
 
 ---
-### Release Notes
-Please add any useful notes about the feature/fix that might be helpful for others.
+### Purpose of this PR
+Why is this PR needed, what hard problem is it solving/fixing?
 
 ---
 ### Testing status
-**Katana Tests**: First off we need to make sure the Katana SRP tests are green?
 
 **Manual Tests**: What did you do?
 - [ ] Opened test project + Run graphic tests locally
 - [ ] Built a player
 - [ ] Checked new UI names with UX convention
-- [ ] Tested UI multi-edition + Undo/Redo
+- [ ] Tested UI multi-edition + Undo/Redo + Prefab overrides + Alignment in Preset
 - [ ] C# and shader warnings (supress shader cache to see them)
 - [ ] Checked new resources path for the reloader (in devloper mode, you have a button at end of resources that check the pathes)
 - Other: 
 
 **Automated Tests**: What did you setup? (Add a screenshot or the reference image of the test please)
 
-Launch Katana (Link on master here - update for your branch):
-https://katana.bf.unity3d.com/projects/com.unity.render-pipelines/builders?ScriptableRenderLoop_branch=master&automation-tools_branch=master&unity_branch=trunk&sort=1-asc
-
-Alternative, launch Yamato (Select your branch):
-https://yamato.prd.cds.internal.unity3d.com/jobs/78-ScriptableRenderPipeline
+**Yamato**: (Select your branch):
+https://yamato.prd.cds.internal.unity3d.com/jobs/902-Graphics
 
 Any test projects to go with this to help reviewers?
 

.github/labeler.yml

@@ -0,0 +1,32 @@
+# Add 'core' to any changes within 'com.unity.render-pipelines.core' folder or any subfolders
+SRP:
+  - com.unity.render-pipelines.core/**/*
+  - TestProjects/SRP*/**/*
+
+# Add 'hdrp' to any changes within HDRP-related folder or any subfolders
+HDRP:
+  - com.unity.render-pipelines.high-definition-config/**/*
+  - com.unity.render-pipelines.high-definition/**/*
+  - com.unity.testing.hdrp/**/*
+  - TestProjects/HDRP*/**/*
+
+Universal:
+  - com.unity.render-pipelines.universal/**/*
+  - com.unity.render-pipelines.lightweight/**/*
+  - TestProjects/Universal*/**/*
+
+Shader Graph:
+  - com.unity.shadergraph/**/*
+  - TestProjects/ShaderGraph*/**/*
+  - com.unity.render-pipelines.universal/Editor/ShaderGraph/*
+
+vfx:
+  - com.unity.visualeffectgraph/**/*
+  - com.unity.testing.visualeffectgraph/**/*
+  - TestProjects/VisualEffectGraph*/**/*
+
+yamato:
+  - .yamato/*
+
+testing:
+  - TestProjects/**/*

.github/workflows/greetings.yml

@@ -0,0 +1,17 @@
+name: Greetings
+on:
+  pull_request:
+    types: [opened, ready_for_review]
+
+jobs:
+  greeting:
+    runs-on: ubuntu-latest
+    if: github.event.pull_request.draft == false
+    steps:
+    - uses: actions/first-interaction@v1
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        pr-message: |
+                 Welcome to the Unity SRP repo!
+                 Please make sure to fill out the PR template as best you can to give reviewers as much information as possible.
+                 If you have any questions (and you are a Unity employee) go to "#devs-renderpipe"

.github/workflows/labeler.yml

@@ -0,0 +1,14 @@
+name: Labeler
+on:
+  pull_request:
+    types: [opened, ready_for_review]
+
+jobs:
+  label:
+
+    runs-on: ubuntu-latest
+    if: github.event.pull_request.draft == false
+    steps:
+    - uses: actions/labeler@v2
+      with:
+        repo-token: "${{ secrets.GITHUB_TOKEN }}"