Update workflow

[Krishanx92]

Purpose

Explain why this feature or fix is required. Describe the underlying problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe what solutions this feature or fix introduces to address the problems outlined above.

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI. Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Automation tests

• Unit tests

  Code coverage information

• Integration tests

  Details about the test cases and coverage

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
• Ran FindSecurityBugs plugin and verified report? yes/no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c1355334-3207-451d-9e47-df82741f8af4

📥 Commits

Reviewing files that changed from the base of the PR and between f833b2a and 9d628bc.

📒 Files selected for processing (1)

• .github/workflows/enforce-design-gate.yml

---

📝 Walkthrough

Updated the design gate workflow to реагировать only when the “Design and Development Status” field changes to Development.

• Removed the old label-based trigger and enforcement logic.
• Added field-based checks to ensure the rule applies only to feature issues.
• If required labels are missing, the workflow now posts a warning comment listing which labels still need to be added.
• If the change is irrelevant or all required labels are present, the workflow exits without commenting.

Walkthrough

The enforce-design-gate GitHub Actions workflow was modified to change its trigger condition and enforcement logic. The trigger now activates on field_added events for the "Design and Development Status" project field when set to Development, replacing the previous labeled/unlabeled event trigger. The enforcement step now checks whether an issue is labeled feature and whether required labels (Design Done, Mail Sent) are present, posting a warning comment listing missing labels when applicable; otherwise it exits without action.

Sequence Diagram(s)

sequenceDiagram
  participant GitHub as GitHub Issues
  participant Workflow as enforce-design-gate Workflow
  participant Issue as Issue Comment API

  GitHub->>Workflow: field_added event (Design and Development Status)
  Workflow->>Workflow: Check field value equals Development
  Workflow->>Workflow: Check issue has feature label
  Workflow->>Workflow: Check for Design Done and Mail Sent labels
  alt Required labels missing
    Workflow->>Issue: Post warning comment with missing labels
  else All labels present or not applicable
    Workflow->>Workflow: Exit without action
  end

Loading

Estimated code review effort: Medium

Related PRs: None identified.

Suggested labels: ci, github-actions

Suggested reviewers: None identified.

Poem

A field once flipped from "labeled" to "field",
The gate now checks what status has revealed.
Design Done, Mail Sent — the labels we seek,
If missing, a comment will surely speak.
No more chasing labels torn away,
Now watching fields shift, day by day. 🐇

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}