search

camunda / camunda-docs

Camunda 8 Documentation, including all components and features
https://docs.camunda.io/
Other
52 stars 180 forks source link

Auto-assign PRs based on changed file paths #1781

Open pepopowitz opened 1 year ago

pepopowitz commented 1 year ago

Part of #1742

We use the PR template to prompt authors to tag @christinaausley and @akeller for review, but this doesn't always happen.

We could write a GitHub action to auto-assign to Christina/Amara when a content folder/file is edited, and Steve/Amara when an infrastructure folder/file is edited.

I think we could define this as simply as "docs"/"versioned_docs"/"optimize"/"optimize_versioned_docs" are content, and everything else is infrastructure. If we wanted, we could also consider .htaccess and sidebars files as content, and auto-tag Christina on those.

akeller commented 3 weeks ago

This is definitely becoming more interesting as we look to have tech writers in specific areas. @conceptualshark WDYT about testing this with your Self-Managed focus area?

conceptualshark commented 3 weeks ago

With the addition of the tech-writers role, I think a simple division between automatically adding tech-writers for content changes/Steve for infra might be appropriate. Anything else (self managed, APIs and Tools, etc) might depend on how the team decides to organize/manage things.

PRs tagging me directly while out on vacation, for example, would need to get caught in a different sweep, instead of just being seen automatically by each of us via the tech-writers @. I don't think github allows you to tag both a team and a member of the team, or that would be the easier solution to me. But I am definitely willing to give it a shot and get the data!