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: create v1.1 directory #942

Merged
merged 2 commits into from
Aug 18, 2023
Merged

Conversation

MarkLodato
Copy link
Member

The spec/v1.1/ directory is a copy of spec/v1.0/, while
_data/nav/v1.1.yml is a copy of v1.0.yml with "1.0" replaced by "1.1".

$ git ls-tree HEAD:docs/spec | grep 'v1.[01]$'
040000 tree 52008aa2d63ee43de55af463c016ea2b6771433a    v1.0
040000 tree 52008aa2d63ee43de55af463c016ea2b6771433a    v1.1

Signed-off-by: Mark Lodato lodato@google.com

The spec/v1.1/ directory is a copy of spec/v1.0/, while
_data/nav/v1.1.yml is a copy of v1.0.yml with "1.0" replaced by "1.1".

```bash
$ git ls-tree HEAD:docs/spec | grep 'v1.[01]$'
040000 tree 52008aa2d63ee43de55af463c016ea2b6771433a    v1.0
040000 tree 52008aa2d63ee43de55af463c016ea2b6771433a    v1.1
```

Signed-off-by: Mark Lodato <lodato@google.com>
@netlify
Copy link

netlify bot commented Aug 16, 2023

Deploy Preview for slsa ready!

Name Link
🔨 Latest commit d99636d
🔍 Latest deploy log https://app.netlify.com/sites/slsa/deploys/64de18126e43dc000898a463
😎 Deploy Preview https://deploy-preview-942--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.

@MarkLodato MarkLodato mentioned this pull request Aug 16, 2023
7 tasks
@MarkLodato
Copy link
Member Author

I don't think our community guidelines make sense for draft branches. While this is technically "content", it is for a new release that is not yet approved so the full 3 reviewers + 72 hours doesn't make sense.

Copy link
Member

@joshuagl joshuagl left a comment

Choose a reason for hiding this comment

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

LGTM

I don't think our community guidelines make sense for draft branches. While this is technically "content", it is for a new release that is not yet approved so the full 3 reviewers + 72 hours doesn't make sense.

Yes, agreed. They are only guidelines and have several edge cases. I think it's fine to have only two reviewers/approvers for this change, so long as edits to the spec meet the documented criteria.

Signed-off-by: Mark Lodato <lodato@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants