-
Notifications
You must be signed in to change notification settings - Fork 359
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
Starts implementation for --force system & establishes naming consistency #1161
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok i guess
Okay it seems to be having problems with paths |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine w/ this landing but would note that the sync and sync-force workflows could, instead of being carbon copies of each other, be shared and extended via decoration using the github reusable workflow pattern. This would result in reduced LOC and ensure these workflows are kept in sync over time as changes are needed in one or the other.
Oh interesting I wasn't aware of that. Will implement! |
@jaspermayone just ping me when u want re-review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renaming the actions is much appreciated :) lgtm!
Docs on --force here octodns/octodns#1170 |
This PR starts the implementation for a
--force
system as well as establishing some constancy for workflow/file naming.See https://hackclub.slack.com/archives/C05SVRTCDGV/p1714867674790609?thread_ts=1714613706.014109&cid=C05SVRTCDGV for why the validation flow is currently blocked, but this PR will at least establish a manual workflow unblocking the other PR's, until we establish an auto labeler / system.