1797 allow local definition of asset type prop values#1821
1797 allow local definition of asset type prop values#1821aj-stein-nist merged 2 commits intodevelopfrom
Conversation
wendellpiez
left a comment
There was a problem hiding this comment.
It looks like a bunch of other changes are committed to this PR - it should be probably be targeting develop or another branch, not main? (@aj-stein-nist can advise)
|
@Arminta-Jenkins-NIST did you push up the commit after editing the branch? I can't rebase to develop because this branch is the same as develop, perhaps you're missing the commit where you edited the requisite files? |
aj-stein-nist
left a comment
There was a problem hiding this comment.
Thanks for pushing this up and doing a quick synchronous review. I provided some changes I would recommend.
|
@Arminta-Jenkins-NIST tomorrow I am going to have to help you reconfigure this branch on your computer. I will rebase it for you now. |
e15d513 to
b057dae
Compare
|
Hi @Arminta-Jenkins-NIST, can you confirm if you made changes locally but forgot to push them up? I see you 👍ed some comments and resolved them, but changes are not in the PR, so it is possible you did not do |
|
@aj-stein-nist I thought I did everything properly. However, yesterday's peering session with @iMichaela on issue #1798 showed there are issues with my local setup. It is still unclear to me what went wrong. |
021d94d to
3dca6c0
Compare
3dca6c0 to
6cdbf59
Compare
Committer Notes
asset-typewill nowallow-othervalues making the property less strictive{Please provide a brief description of what this PR accomplishes. Be sure to reference any issues addressed. If the PR is a work-in-progress submitted for early review, please include [WIP] at the beginning of the title or mark the PR as DRAFT.}
All Submissions:
By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.
(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)
Changes to Core Features:
Have you written new tests for your core changes, as applicable?Have you included examples of how to use your new feature(s)?Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.