Skip to content

Release/26.07.16 - #208

Open
perrymanmd wants to merge 9 commits into
mainfrom
release/26.07.16
Open

Release/26.07.16#208
perrymanmd wants to merge 9 commits into
mainfrom
release/26.07.16

Conversation

@perrymanmd

Copy link
Copy Markdown
Contributor

First cut of script to update release/26_02_17 to release/26_07_16

@MikeNeilson MikeNeilson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Marking as request changes so it doesn't get merged to main.

branches are deleted on merge (though release/*) should be protected.

If these changes should be merged into main, a separate branch specific to that action should be created.

However, it is likely best we do that after we have confirmed all of the schema update operations.

@perrymanmd

Copy link
Copy Markdown
Contributor Author

Marking as request changes so it doesn't get merged to main.

branches are deleted on merge (though release/*) should be protected.

If these changes should be merged into main, a separate branch specific to that action should be created.

However, it is likely best we do that after we have confirmed all of the schema update operations.

Okay - I just made the PR because that the update script and dependencies should be available for future branches off main.

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