docs: Pull Request Support documentation added

Author: luisfalconmx

README.md

@@ -23,7 +23,7 @@ To overcome this limitation, and help developers such as myself automate this te
 | `GLOBAL_TEMPLATE_REPOSITORY` | you can set a global repository template where all the files are stored. | `false`
 | `committer_name` | Specify the committer name | `Dynamic Readme` |
 | `committer_email` | Specify the committer email | `[email protected]` |
-| `commit_message` | set a custom commit message | `💬 - File Rebuilt | Github Action Runner : ${GITHUB_RUN_NUMBER}` |
+| `commit_message` | set a custom commit message | ` 💬 - File Rebuilt | Github Action Runner : ${GITHUB_RUN_NUMBER} ` |
 | `confirm_and_push` | Commit the changes and push directly to repository | `true` |
 <!-- END RAW_CONTENT -->
 
@@ -147,6 +147,54 @@ Reusable Includes Custom Markdown :
 >
 > :information_source: Even though **Reusable includes** and **Inline Includes** do the same work, they can come in handy when you are generating a template and saving it in the same file. It preserves the include comment which will be parsed again when re-generating the template, and the contents of the include will be updated accordingly.
 
+###  Pull Request Support
+
+This action modifies the files, creates a commit and uploads them directly to the default branch of the repository.
+
+If the default branch of the repository is protected by the rule `Require a pull request before merging` then you will need to set the option `confirm_and_push: false` so that the commit is not made and the changes are not uploaded to the default branch.
+
+``` yaml
+- name: "💫  Dynamic Template Render"
+  uses: varunsridharan/action-dynamic-readme@main
+  with:
+    GLOBAL_TEMPLATE_REPOSITORY: {repository-owner}/{repository-name}
+    files: |
+      FILE.md
+      FILE2.md=output_filename.md
+      folder1/file.md=folder2/output.md
+    confirm_and_push: false # Important if use "Require a pull request before merging" rule
+  env:
+    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+```
+
+In addition to the previous configuration, it is necessary to use other actions to be able to confirm the changes and generate a Pull Request towards the default branch
+
+``` yaml
+- name: "📥  Fetching Repository Contents"
+  uses: actions/checkout@main
+
+- name: "💫  Dynamic Template Render"
+  uses: varunsridharan/action-dynamic-readme@main
+  with:
+    GLOBAL_TEMPLATE_REPOSITORY: {repository-owner}/{repository-name}
+    files: |
+      FILE.md
+      FILE2.md=output_filename.md
+      folder1/file.md=folder2/output.md
+    confirm_and_push: false # Important if use "Require a pull request before merging" rule
+  env:
+    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+- name: Create pull request
+  uses: peter-evans/create-pull-request@v3
+  with:
+    token: ${{ secrets.GITHUB_TOKEN }}
+```
+
+Thanks to this configuration, the necessary files can be dynamically generated by adding them to a different branch that then we can merge with the default branch, complying with the rule `Require a pull request before merging`.
+
+Check out the example workflow (Pull Request Support) for a more advanced configuration
+
 ---
 
 <h3 align="center"> For live Demo Please Check <a href="https://github.com/varunsridharan/demo-dynamic-readme">Demo Repository</a> </h3>
@@ -191,7 +239,7 @@ jobs:
 
 <!-- END RAW_CONTENT -->
 
-## 🚀 Example Workflow File (Pull Request)
+## 🚀 Example Workflow File (Pull Request Support)
 
 <!-- START RAW_CONTENT -->
 ```yaml