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

[RECUR-186] Fix issue where original version had no ApiVersionSetId set #138

Merged
merged 1 commit into from
Jul 25, 2024

Conversation

ebronson68
Copy link
Contributor

@ebronson68 ebronson68 commented Jul 25, 2024

RECUR-186
Summary [DEVOPS] Research how to deploy v1 and v2 APIs separately
Type Story Story
Status In Progress
Points N/A
Labels -
---

Description

  • Fix issue where original version had no ApiVersionSetId set

Related Links

  • Jira Issue: JIRA-XXX

@ebronson68 ebronson68 requested a review from a team as a code owner July 25, 2024 17:29
@ebronson68 ebronson68 merged commit ca27077 into main Jul 25, 2024
4 checks passed
@ebronson68 ebronson68 deleted the story/RECUR-186/avoid-api-exists-conflicts branch July 25, 2024 17:29
@github-actions github-actions bot added devops DevOps Team Recurly Implementation story New feature or request labels Jul 25, 2024
Copy link

Knock Knock! 🔍

Just thought I'd let you know that your PR title and story title look quite different. PR titles that closely resemble the story title make it easier for reviewers to understand the context of the PR.

An easy-to-understand PR title a day makes the reviewer review away! 😛⚡️
Story Title [DEVOPS] Research how to deploy v1 and v2 APIs separately
PR Title [RECUR-186] Fix issue where original version had no ApiVersionSetId set

Check out this guide to learn more about PR best-practices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops DevOps Team Recurly Implementation story New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant