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

[KED-2961] Move scripts from private-kedro-sync to develop #1125

Merged
merged 6 commits into from
Dec 17, 2021

Conversation

antonymilne
Copy link
Contributor

@antonymilne antonymilne commented Dec 17, 2021

Description

With any luck this is the final PR in the migration of scripts from private-kedro-sync to kedro... It is the version of #1107 that goes to develop rather than main.

The sync job already applied almost all the changes that were required. All that was left was to swap Python 3.6 for 3.9 in a couple more places.

Note I added the new docker builds as per https://github.com/quantumblacklabs/private-kedro-sync/pull/35/. Unlike what that PR says, since this is all one one repo now this is fine to merge now because docker_build will only run on main and not develop.

Checklist

  • Read the contributing guidelines
  • Opened this PR as a 'Draft Pull Request' if it is work-in-progress
  • Updated the documentation to reflect the code changes
  • Added a description of this change in the RELEASE.md file
  • Added tests to cover my changes

@antonymilne antonymilne changed the base branch from main to develop December 17, 2021 16:46
@antonymilne antonymilne changed the title Feature/move sync dev#ked 2961 [KED-2961] Move scripts from private-kedro-sync to develop Dec 17, 2021
@antonymilne antonymilne self-assigned this Dec 17, 2021
@antonymilne antonymilne marked this pull request as ready for review December 17, 2021 16:58
# Conflicts:
#	.circleci/config.yml
#	tools/circleci/docker_build_img/build.sh
@datajoely datajoely merged commit 35e78cc into develop Dec 17, 2021
@antonymilne antonymilne deleted the feature/move-sync-dev#ked-2961 branch December 17, 2021 17:33
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