Skip to content

ci: added workflow to check if issue is linked with pr#1106

Merged
PritishBudhiraja merged 1 commit into
mainfrom
ci/issue-check
Jul 17, 2025
Merged

ci: added workflow to check if issue is linked with pr#1106
PritishBudhiraja merged 1 commit into
mainfrom
ci/issue-check

Conversation

@aritro2002

@aritro2002 aritro2002 commented Jul 16, 2025

Copy link
Copy Markdown
Contributor

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

I have created issue for checking if any issue is linked with the pr.

How did you test it?

Case 1: If no issue is linked
Screenshot 2025-07-16 at 6 21 43 pm
Screenshot 2025-07-16 at 6 22 04 pm
Screenshot 2025-07-16 at 6 22 36 pm

Case 2: If issue is linked
Screenshot 2025-07-16 at 6 26 57 pm

Case 3: If issue is delinked, we rerun the workflow jobs
Screenshot 2025-07-16 at 6 30 10 pm
Screenshot 2025-07-16 at 6 30 21 pm

Case 4: If we relink
Screenshot 2025-07-16 at 6 31 24 pm

Checklist

  • I ran npm run re:build
  • I reviewed submitted code
  • I added unit tests for my changes where possible

@semanticdiff-com

semanticdiff-com Bot commented Jul 16, 2025

Copy link
Copy Markdown

Review changes with  SemanticDiff

Changed Files
File Status
  .github/workflows/check-linked-issue.yml  0% smaller

@github-actions

Copy link
Copy Markdown
Contributor

❌ Missing Linked Issue

This pull request needs to be linked to at least one issue before it can be merged.

How to link an issue:

  1. Add keywords to PR description:

    • Fixes #123
    • Closes #456
    • Resolves #789
    • Fixes #123, #456, and #789 (multiple issues)
  2. Reference issue in PR title or description:

    • #123
    • Issue #456
    • Addresses #123 and #456 (multiple issues)
  3. Use GitHub's UI:

    • Go to the "Development" section in the right sidebar
    • Click "Link an issue"
    • Select the relevant issue(s)

💡 Tip: You can link multiple issues using any combination of the above methods!

Once you've linked at least one issue, this check will automatically pass! 🚀

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

❌ Missing Linked Issue

This pull request needs to be linked to at least one issue before it can be merged.

How to link an issue:

  1. Add keywords to PR description:

    • Fixes #123
    • Closes #456
    • Resolves #789
    • Fixes #123, #456, and #789 (multiple issues)
  2. Reference issue in PR title or description:

    • #123
    • Issue #456
    • Addresses #123 and #456 (multiple issues)
  3. Use GitHub's UI:

    • Go to the "Development" section in the right sidebar
    • Click "Link an issue"
    • Select the relevant issue(s)

💡 Tip: You can link multiple issues using any combination of the above methods!

Once you've linked at least one issue, this check will automatically pass! 🚀

@github-actions

Copy link
Copy Markdown
Contributor

❌ Missing Linked Issue

This pull request needs to be linked to at least one issue before it can be merged.

How to link an issue:

  1. Add keywords to PR description:

    • Fixes #123
    • Closes #456
    • Resolves #789
    • Fixes #123, #456, and #789 (multiple issues)
  2. Reference issue in PR title or description:

    • #123
    • Issue #456
    • Addresses #123 and #456 (multiple issues)
  3. Use GitHub's UI:

    • Go to the "Development" section in the right sidebar
    • Click "Link an issue"
    • Select the relevant issue(s)

💡 Tip: You can link multiple issues using any combination of the above methods!

Once you've linked at least one issue, this check will automatically pass! 🚀

@aritro2002 aritro2002 linked an issue Jul 16, 2025 that may be closed by this pull request
@aritro2002 aritro2002 added the Ready for Review PR with label Ready for Review should only be reviewed. label Jul 16, 2025
@PritishBudhiraja PritishBudhiraja merged commit da558e3 into main Jul 17, 2025
17 of 20 checks passed
@PritishBudhiraja PritishBudhiraja deleted the ci/issue-check branch July 17, 2025 02:47
@github-actions github-actions Bot added the Closed Label will be automatically added when the PR will get merged to main label Jul 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Closed Label will be automatically added when the PR will get merged to main Ready for Review PR with label Ready for Review should only be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

create workflow to check if issue is linked with pr or not

2 participants