Assign issue reporting to other person

[CAMOBAP]

My GitHub account mentioned for issue reporting in many places in metanorma, please reassign it to another team member

• https://github.com/metanorma/ci/blob/main/.github/workflows/ci-repo-watcher.yml#L48
• https://github.com/metanorma/ci/blob/main/cimas-config/cimas.yml#L6
• https://github.com/metanorma/mnconvert-ruby/blob/ce48199d32a4fe4d75db36b8d0ff6555c73d37c0/.github/workflows/release-tag.yml#L63
• https://github.com/metanorma/mn2pdf-ruby/blob/60ced1aa5b66fba82e5e78c4376ab1413de179ca/.github/workflows/release.yml#L61
• https://github.com/metanorma/mn2sts-ruby/blob/6e9955b6ec799855c0ea5ac371424ef367e7664c/.github/workflows/release.yml#L58
• https://github.com/metanorma/sts2mn-ruby/blob/2081cad6aed760cb37d9a27a1c958767579c9396/.github/workflows/release-tag.yml#L53
• https://github.com/metanorma/metanorma-cli/blob/009e04769963cd217e6c8b46036e75a04f53d24c/.github/workflows/fonts-check.yml#L107
• https://github.com/metanorma/sts2mn-ruby/blob/2081cad6aed760cb37d9a27a1c958767579c9396/.github/workflows/release.yml#L58
• https://github.com/metanorma/mn2sts-ruby/blob/6e9955b6ec799855c0ea5ac371424ef367e7664c/.github/workflows/release-tag.yml#L53
• https://github.com/relaton/support/blob/124f786dd4a9074046b31321cb3a40f7c41316a2/cimas-config/cimas.yml#L5

cc @ronaldtse

[opoudjis]

Surfacing where this sits in the cimas/ci rehabilitation arc, leaving open as a real cleanup task that needs maintainer input.

The substance — replacing @ronaldtse's GitHub handle in the issue-reporting destinations of:

• metanorma/ci/.github/workflows/ci-repo-watcher.yml#L48
• metanorma/ci/cimas-config/cimas.yml#L6
• the listed release.yml files in mnconvert-ruby, mn2pdf-ruby, mn2sts-ruby, sts2mn-ruby, metanorma-cli/fonts-check.yml
• relaton/support/cimas-config/cimas.yml#L5

— is small and centralisable through cimas-sync once a target handle is decided. The cimas-side patches mode (added in cimas#38) is the right vector for the sweep across the *-ruby tooling repos; the per-repo locations in mnconvert-ruby et al. would be touched by the same Section 5 hygiene pass currently tracked in the rehabilitation arc roadmap ("6 *-ruby tooling repos needing custom one-off edits").

Blocker: the ticket doesn't specify who should receive the reassigned reporting. The replacement target needs to be decided by the maintainer (Ronald, or whoever the rotation lands on) before the sweep can run, otherwise the substitute creates a new instance of the same problem.

Leaving open. Pinging — when a target handle is decided, the sweep itself is a small cimas-patches PR (across metanorma/ci's cimas.yml + relaton/support's cimas.yml) plus the 6 *-ruby repos' release.yml files (folds into the arc Section 5 hygiene pass).

🤖