Adding Most Recent Data Bites presentation

[jjahearn22]

Committer Notes

Adding the most recent Data Bites presentation

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• If applicable, have all FedRAMP Documents Related to OSCAL Adoption affected by the changes in this issue have been updated.?
• If applicable, does this PR reference the issue it addresses and explain how it addresses the issue?
• Have you squashed any non-relevant commits and commit messages? [instructions] Has merge commit, will fix up and then merge into master.

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

[aj-stein-gsa]

@jjahearn22 can you please follow the PR checklist and allow maintainers to modify your PR branch? If not, I will need you to rebase for me. Thanks!

[jjahearn22]

@jjahearn22 can you please follow the PR checklist and allow maintainers to modify your PR branch? If not, I will need you to rebase for me. Thanks!

Hi @aj-stein-gsa , the checkbox is ticked to "allow edits by maintainers" - going through the checklist, and I believe I've settled everything. Let me know if it's not looking that way on your end.

[aj-stein-gsa]

Hi @aj-stein-gsa , the checkbox is ticked to "allow edits by maintainers" - going through the checklist, and I believe I've settled everything. Let me know if it's not looking that way on your end.

Yeah, thanks for doing that. Interestingly, it seems to still deny probably because it is using your copy of the master branch and GitHub may protect that more stringently. I typically clean up merge commits like yours because later, when spelunking and trying to review history commit by commit, it makes the history messy and confusing.

I will merge this into another branch and then clean it up and delete them, unless you know how to rebase. If not, no worries there.

[aj-stein-gsa]

Sigh, and GitHub took care of it anyway, apologies (I forgot about the squash and cleanup logic they use, I have had less success with that).