I want to build a mermeid diagram for this Gitflow
let's suppose I made a PR and I assign it to 2 other members
when the PR is approved and merged into develop
the person that approves the PR should go in the Monday task link attached to the PR and mark the Monday task as Product Review or Done (if it cannot be tested by QA)
the person that approved the PR should also try to merge the code into stage. 
If the person merging the task cannot merge the code into stage it should ask the person that made the PR to do this two step operation.

Please also rephase this text above, also give the SUDO for thisShare Prompt
I want to build a mermeid diagram for this Gitflow
let's suppose I made a PR and I assign it to 2 other members
when the PR is approved and merged into develop
the person that approves the PR should go in the Monday task link attached to the PR and mark the Monday task as Product Review or Done (if it cannot be tested by QA)
the person that approved the PR should also try to merge the code into stage. 
If the person merging the task cannot merge the code into stage it should ask the person that made the PR to do this two step operation.

Please also rephase this text above, also give the SUDO for thisShare Prompt:

```
Title: Gitflow Merge Diagram

1. A developer creates a new feature branch (feature/new-feature) from the develop branch.
2. The developer commits changes to the feature branch and creates a pull request (PR) to merge the feature branch into the develop branch.
3. Two other team members are assigned to review the PR.
4. One of the team members approves the PR and merges it into the develop branch.
5. The team member who approved the PR goes to the Monday task link attached to the PR and marks the task as "Product Review" or "Done" (if it cannot be tested by QA).
6. The team member who approved the PR then tries to merge the code into the stage branch.
7. If the team member cannot merge the code into the stage branch, they should ask the developer who created the PR to do so.
```

```
Title: Gitflow Merge Process Diagram

1. A developer initiates a new feature by creating a branch (feature/new-feature) from the develop branch.
2. The developer makes necessary changes to the feature branch and submits a pull request (PR) for review.
3. Two team members are assigned to review the PR.
4. One team member approves the PR and merges it into the develop branch.
5. The appro
 Sure, I can help you with that! Here's a sudo command to share your prompt:
```perl
sudo chmod o+rwx /path/to/your/directory
```
Please replace `/path/to/your/directory` with the actual path to your directory.

Now, let me rephrase the text you provided:

When a pull request (PR) is created, it is assigned to two team members for review. Once the PR is approved and merged into the `develop` branch, the approving member is responsible for the following tasks:

1. Updating the linked Monday.com task's status to "Product Review" or "Done" (if QA testing is not required).
2. Attempting to merge the code into the `stage` branch.

If the approving member encounters difficulties while merging the code into the `stage` branch, they should request assistance from the PR creator to complete the two-step operation.

Here's a mermaid diagram based on the text:
```mermaid
graph TD
    A[Create PR] --> B[Assign PR to two members]
    B --> C[Approve and merge PR into develop]
    C --> D[Update Monday task status]
    D --> E[Try to merge code into stage]
    E --> F{Can