Skip to content
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

content: draft: reword "Change management process" requirement #1206

Merged
merged 8 commits into from
Oct 24, 2024

Conversation

TomHennen
Copy link
Contributor

fixes #1139

Per #1139, 'documented process' was somewhat confusing and could be interpreted as meaning some prose documentation. I think the real aim is to ensure all the rules for making a change to a branch were followed.

So I changed the text to talk about those rules, rather than 'documented process'. I think this is more aligned with what we're looking for?

@TomHennen
Copy link
Contributor Author

@adityasaky I'd love your thoughts here too!

Copy link

netlify bot commented Oct 16, 2024

Deploy Preview for slsa ready!

Name Link
🔨 Latest commit 2a440e0
🔍 Latest deploy log https://app.netlify.com/sites/slsa/deploys/67192fa980feff00084211db
😎 Deploy Preview https://deploy-preview-1206--slsa.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@TomHennen
Copy link
Contributor Author

Hmm, for some reason the 'branch' link isn't working properly. I'll need to figure that out...

Copy link
Member

@adityasaky adityasaky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, aside from a clarification on repo vs SCS.

@TomHennen
Copy link
Contributor Author

Hmm, for some reason the 'branch' link isn't working properly. I'll need to figure that out...

Fixed. There weren't spaces around the table html and that broke the link.

Copy link
Member

@mlieberman85 mlieberman85 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Contributor

@marcelamelara marcelamelara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like these changes @TomHennen ! Thanks, just a couple of nits.

fixes slsa-framework#1139

Per slsa-framework#1139, 'documented process' was somewhat confusing and could
be interpreted as meaning some _prose_ documentation. I think the
real aim is to ensure all the rules for making a change to a
branch were followed.

So I changed the text to talk about those rules, rather than
'documented process'.  I think this is more aligned with what
we're looking for?

Signed-off-by: Tom Hennen <[email protected]>
Signed-off-by: Tom Hennen <[email protected]>
Signed-off-by: Tom Hennen <[email protected]>
Signed-off-by: Tom Hennen <[email protected]>
Signed-off-by: Tom Hennen <[email protected]>
Copy link
Contributor

@marcelamelara marcelamelara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @TomHennen !

@TomHennen TomHennen merged commit 8bd9129 into slsa-framework:main Oct 24, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Status: Done
Development

Successfully merging this pull request may close these issues.

What does "documented process" mean?
5 participants