add in docs that a build log file is generated

Signed-off-by: habibayassin <[email protected]>

Author: habibayassin

.github/ISSUE_TEMPLATE/bug_report_with_orfs.yml

@@ -100,7 +100,9 @@ body:
     id: logs
     attributes:
       label: Relevant log output
-      description: Feel free to add any relevant log snippets to this section. This will be automatically formatted into code, so no need for backticks.
+      description: |
+        You can upload `build_openroad.log` file found in the main directory by dragging and dropping it below.
+        Feel free to add any other relevant log snippets to this section. This will be automatically formatted into code, so no need for backticks.
       render: shell
     validations:
       required: false

docs/contrib/DeveloperGuide.md

@@ -2,7 +2,7 @@
 
 ## Building
 
-Instructions for building are available [here](../user/GettingStarted.md).
+Instructions for building are available [here](getting:started:setup:build).
 
 ## Logger
 

docs/user/BuildLocally.md

@@ -27,6 +27,10 @@ cd OpenROAD-flow-scripts
 ./build_openroad.sh --local
 ```
 
+```{note}
+There is a `build_openroad.log` file that is generated with every build in the main directory. In case of filing issues, it can be uploaded in the "Relevant log output" section of OpenROAD-flow-scripts repo [issue form](https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/issues/new?assignees=&labels=&template=bug_report_with_orfs.yml).
+```
+
 ## Verify Installation
 
 The binaries should be available on your `$PATH` after setting up the

docs/user/GettingStarted.md

@@ -21,7 +21,7 @@ To build the binaries and run `gcd` through the flow:
 Larger designs may require better hardware.
 
 ---
-
+(getting:started:setup:build)=
 ### Building and Installing the Software
 
 **WARNING**