Added a process flow diagram for better explainability

docs/process-flow.md

@@ -0,0 +1,41 @@
+## captures how the GHAS-Reviewer app will work when alerts are dismissed by Developers on the GitHub UI
+
+## The process flow is as follows:
+
+1. The Developer dismisses the alert on the GitHub UI
+2. A webhook is triggered and sends a payload to the GHAS-Reviewer app
+3. The GHAS-Reviewer app receives the payload and processes it
+4. If the alert dismissed is a dependabot, code scanning or secret scanning alert, the GHAS-Reviewer app will check if the alert is dismissed by the Developer
+5. If the alert is dismissed by the Developer, the GHAS-Reviewer app will re-open the alert on the GitHub UI, and assign it to a member of the Security team
+6. The Security team member will review the alert and take necessary actions, such as dismissing the alert, or creating an issue to fix the vulnerability
+
+
+## Sequence Diagram
+
+```mermaid
+sequenceDiagram
+    participant Developer
+    participant GitHub-UI
+    participant GHAS-Reviewer
+    participant SecurityTeam
+
+
+    Note over Developer: Encounters Dependabot, Code Scanning, Secret Scanning alerts within PR
+    Developer->>GitHub: Dismisses alert on the GitHub UI
+    GitHub->>GHAS-Reviewer: Calls registered Webhook with alert payload
+    GHAS-Reviewer->>GHAS-Reviewer: Processes payload and understands alert type, dismmisser
+    critical Determine who dismissed the alert
+        GHAS-Reviewer-->>GitHub: Dismissed by Developer?
+    option Yes
+        Note over GHAS-Reviewer: Re-open alert and assign to Security Team
+        GHAS-Reviewer->>GitHub: Re-open alert
+        GHAS-Reviewer->>SecurityTeam: Assign alert
+        SecurityTeam->>GHAS-Reviewer: Review alert
+        SecurityTeam->>GitHub: Dismiss alert
+    option No
+        Note over GHAS-Reviewer: Alert dismissed by Security team member
+        GHAS-Reviewer->>GitHub: Alert remains dismissed, no action required
+
+    end
+```
+