Skip to content
Snippets Groups Projects

Draft: docs: adding mermaid sequence diagram displaying the current picture

Open Jordi Gómez requested to merge gnugomez/main/sequence-diagram into main

I'm opening this MR to facilitate discussions around adding a sequence diagram. This will help us better understand the runtime flow and interactions between various actors involved in the project. The diagram won't aim to exhaustively define internal validation logic, but rather illustrate the relationships and calls required for git-eca to complete its task effectively.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Jordi Gómez requested review from @malowe and @gnugomez

    requested review from @malowe and @gnugomez

  • Author Developer

    @malowe I applied the notes you shared with me as best as I could. If you have time, please take a look.

    • That looks close enough for the most part, though I'd update GitLab Pre-receive Hook to be Other ECA validation requests. There are some GitHub actions that call the validation outside of the context of GitHub pull requests. It's weird, but it's a case that is used in enough places to bear mentioning.

      I'd also update a few other things, namely the name of the h2 to Current general validation flow and to update the TOC at the top of the file. There's a neat plugin for VS Code called Markdown All in One that can take care of Tables of contents for you which is super handy.

    • Author Developer

      Nice to hear that!

      I'll apply what you mentioned, and I think I'll also be adding the Mermaid diagram VS Code extension to the list.

    • Please register or sign in to reply
Please register or sign in to reply
Loading