Closed wbohlken closed 2 months ago
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.
:white_check_mark: schnuerle
:x: Wouter Bohlken
Looks good @wbohlken! Make sure to sign this digital license agreement then I can merge your changes to dev.
Hi @schnuerle, thanks for the review. I signed the agreement, can this be merged?
Hi @wbohlken GitHub is still showing me the license agreement is not signed yet. Could you try again here? Here's what I'm seeing:
Hi @schnuerle , that's odd, I signed it multiple times. Just did it again, does it work now?
Not sure what went wrong, but I went ahead and made the same edit myself with #902, so we can close this issue and you are all set. Thank you!
Hi @schnuerle, perfect, thank you!
name: Default about: Suggest changes to MDS title:
MDS Pull Request
Thank you for your contribution! Please review our OMF contributing page to understand guidelines and policies for participation, and our Code of Conduct page.
To avoid complications and help make the Review process as smooth as possible, make sure to:
dev
branch. Please ensure you are targetingdev
, notmain
.Explain pull request
Please provide a clear and concise reason for this pull request and the impact of the change
Is this a breaking change
A breaking change would require consumers or implementors of the API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint).
Impacted Spec
Which spec(s) will this pull request impact?
agency
policy
provider
Additional context
Add any other context or screenshots about the feature request here.