-
Notifications
You must be signed in to change notification settings - Fork 52
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
[Hardware sync] - deployment form - add periodic hardware sync checkbox ui #3745
Conversation
846495d
to
c2945fa
Compare
c2945fa
to
66ac7bb
Compare
66ac7bb
to
bb5da4b
Compare
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.
...onents/MachineHeaderForms/ActionFormWrapper/DeployForm/DeployFormFields/DeployFormFields.tsx
Outdated
Show resolved
Hide resolved
...s/MachineHeaderForms/ActionFormWrapper/DeployForm/DeployFormFields/DeployFormFields.test.tsx
Outdated
Show resolved
Hide resolved
...onents/MachineHeaderForms/ActionFormWrapper/DeployForm/DeployFormFields/DeployFormFields.tsx
Outdated
Show resolved
Hide resolved
Thanks! I filed a bug for this in react-components, but I'll use a custom element in the meantime like we do for other checkboxes on this page. |
Hi @petermakowski I went to take another look at this, but it now appears to include a bunch of unrelated commits. |
e430366
to
518b5f5
Compare
Rebased, should be all good now. |
These changes have been already merged in #3759 |
Done
Screenshots
QA
MAAS deployment
To run this branch you will need access to one of the following MAAS deployments:
Running the branch
You can run this branch by:
QA steps
/MAAS/r/machine/7c7ya3/summary
Fixes
Fixes: canonical-web-and-design/app-tribe/issues/779
Launchpad issue
Related Launchpad maas issue in the form
lp#number
.Backports
In general, please propose fixes against master rather than release branches (e.g. 2.7), unless the fix is only applicable for that specific release. Please apply backport labels to the PR (e.g. "Backport 2.7") for the appropriate releases to target.
Only bug and security fixes should be backported, new features should only land in master.