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
### Rephrased Text

I want to create a Mermaid diagram to illustrate our Git flow process. Let's say I submitted a Pull Request (PR) and assigned it to two other team members for review. Once the PR is approved and merged into the `develop` branch, the approver should go to the Monday task link associated with the PR and update the task status to either "Product Review" or "Done" (if it cannot be tested by QA). Additionally, the approver should attempt to merge the code into the `stage` environment. If they are unable to do this, they should request the original author of the PR to perform these two steps.

### Mermaid Diagram Syntax (SUDO)

Here’s a basic structure for a Mermaid diagram representing the workflow you've described:

```mermaid
graph TD;
    A[Submit PR] --> B[Assign PR to 2 members];
    B --> C[PR Approval];
    C --> D[Merge PR into develop];
    D --> E[Update Monday task status];
    
    E -->|If QA cannot test| F[Mark as Done];
    E -->|If QA can test| G[Mark as Product Review];
    
    C --> H[Attempt to merge into stage];
    H -->|Success| I[Code merged into stage];
    H -->|Failure| J[Request author to merge];
    
    J --> K[Author merges code into stage];
```

### Explanation of the Diagram

- **
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