Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link issue to PR #28717

Open
victoralfaro-dotcms opened this issue May 31, 2024 · 1 comment · Fixed by #30266 or #30317
Open

Link issue to PR #28717

victoralfaro-dotcms opened this issue May 31, 2024 · 1 comment · Fixed by #30266 or #30317

Comments

@victoralfaro-dotcms
Copy link
Contributor

victoralfaro-dotcms commented May 31, 2024

User Story

As a dev-ops engineer, I want to mention the recently created PR url in its corresponding issue in a comment to keep track of PRs and for them to be easily accessible from the issue itself.

Acceptance Criteria

  • When a PR is created then add a comment to the issue mentioning the PR url

dotCMS Version

master

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

  • Slack Conversation: [link]
  • Support Ticket: [link]
  • Figma Design: [link]

Assumptions & Initiation Needs

  • Access to the PR and issue tracking system.
  • Branch naming conventions must allow linking PRs to issues.
  • Permissions to modify and deploy changes to the PR merging workflow.

Quality Assurance Notes & Workarounds

  • Verify that the detection of the last or only PR is accurate.
  • Ensure the Merged label is correctly added to the issue.
  • Perform regression testing to ensure no existing functionality is broken.
Copy link

github-actions bot commented Oct 9, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment