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

LNP-866: Enable Chemlsford Content Hub #712

Merged
merged 1 commit into from
Jul 24, 2024

Conversation

sweetymj
Copy link
Contributor

Context

Does this issue have a Jira ticket?
LNP-866
If this is an issue, do we have steps to reproduce?
N/A

Intent

Make Chelmsford hub available

What changes are introduced by this PR that correspond to the above ticket?
Adding (reverting) Chelmsford to establishment data and ingress.

Would this PR benefit from screenshots?
No

Considerations

Is there any additional information that would help when reviewing this PR?
No
Are there any steps required when merging/deploying this PR?
No

Checklist

  • This PR contains only changes related to the above ticket
  • Tests have been added/updated to cover the change
  • Documentation has been updated where appropriate
  • Tested in Development

@sweetymj sweetymj requested review from Eli-TW and psoleckimoj July 24, 2024 12:05
Copy link
Contributor

@psoleckimoj psoleckimoj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@sweetymj sweetymj merged commit 56af837 into main Jul 24, 2024
6 of 7 checks passed
@sweetymj sweetymj deleted the feature/LNP-866-enable-chelmsford branch July 24, 2024 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants