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

Use cloudposse.tools instead of git.io #315

Merged
merged 3 commits into from
Apr 26, 2022
Merged

Use cloudposse.tools instead of git.io #315

merged 3 commits into from
Apr 26, 2022

Conversation

osterman
Copy link
Member

what

  • Update to use cloudposse.tools instead of git.io

why

  • git.io is shutting down 2022-04-29

references

@osterman osterman requested review from a team as code owners April 26, 2022 16:17
@osterman osterman added the do not merge Do not merge this PR, doing so would cause problems label Apr 26, 2022
@github-actions github-actions bot requested review from aknysh and goruha April 26, 2022 16:18
@osterman
Copy link
Member Author

Waiting on DNSSEC propagation for cloudposse.tools

@osterman osterman removed do not merge Do not merge this PR, doing so would cause problems modules/codefresh labels Apr 26, 2022
Benbentwo
Benbentwo previously approved these changes Apr 26, 2022
nitrocode
nitrocode previously approved these changes Apr 26, 2022
README.yaml Outdated Show resolved Hide resolved
@Nuru Nuru added the no-release Do not create a new release (wait for additional code changes) label Apr 26, 2022
@osterman osterman merged commit c1e13cb into master Apr 26, 2022
@osterman osterman deleted the git-io-deprecation branch April 26, 2022 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
modules/codefresh no-release Do not create a new release (wait for additional code changes)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants