Skip to content

Update for repo rename #93

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

Merged
merged 1 commit into from
Jun 30, 2023
Merged

Conversation

ciroque
Copy link
Collaborator

@ciroque ciroque commented Jun 30, 2023

Proposed changes

The repo has been renamed, this will propagate the new name in the code

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING document
  • If applicable, I have added tests that prove my fix is effective or that my feature works
  • If applicable, I have checked that any relevant tests pass after adding my changes
  • I have updated any relevant documentation (README.md and CHANGELOG.md)

@ciroque ciroque force-pushed the rename-to-nginx-loadbalancer-kubernetes branch from dc77b3f to 583f700 Compare June 30, 2023 18:33
@ciroque ciroque changed the title Update README Update for repo rename Jun 30, 2023
Penultimate pass
Update miscellany
Update deployment
Update application
Update Dockerfile
Update source files
Update README
@ciroque ciroque force-pushed the rename-to-nginx-loadbalancer-kubernetes branch from bf34f76 to 5580a95 Compare June 30, 2023 19:16
@ciroque ciroque marked this pull request as ready for review June 30, 2023 19:23
@ciroque ciroque requested a review from chrisakker as a code owner June 30, 2023 19:23
Copy link
Collaborator

@chrisakker chrisakker left a comment

Choose a reason for hiding this comment

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

Approved

@chrisakker chrisakker merged commit 4b2b3aa into main Jun 30, 2023
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