Create automation workflows for different repos inside one org #141681
Replies: 1 comment
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Feature Area
Projects
Body
Hi,
Currently, my team and I have moved to GitHub Projects, and we are having difficulty getting updated status of the issue and often experience misunderstandings. We need help to advise us on whether any of these can be resolved by any github workflows. I have listed them below and hope for the best. Thank you so much!
Scenario 1: Automatically update assignees when an issue has a comment containing a PR link from another repository
When developer pastes a link of a PR from a different repo in the comment section of my open issue
Then automatically remove all existing assignees from my open issue and replace them with the name of the person who commented with the link.
Scenario 2: Automatically update the label of the issue according to its status in the GitHub project.
For an issue that is linked to a GitHub project, when a developer updates the status of the issue to "In dev" and updates the team for the issue to "Android Native," "iOS Native," "BE," or "Web,"
Then the label of the issue will be updated accordingly to “android-in-dev”, “ios-in-dev”, “api-in-dev”, “web-chat-in-dev”. Multiple labels cannot coexist simultaneously.
Scenario 3: Automatically comment to tag the QA team in the comment of the issue based on the issue's status.
For an issue that is linked to a GitHub project, when a developer updates the status of the issue to "Ready to QA,"
Then the issue wil automatically have a comment saying, "This is ready for @qa to test in the QA environment.”
Scenario 4: Automatically comment to tag the QA team in the comment of the issue based on the status of the PR.
When the PR status is merged into the main branch,
Then the issue linked to the PR will receive a comment saying, "This is ready for @qa to test in the UAT environment.”
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions