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

fix: typo #2084

Merged
merged 2 commits into from
Oct 26, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion adr/0009-sbom-more-than-images.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Potential considerations:
2. Run Syft against files and dataInjections
Pros:
- We know these files are actually inside of the package and won't just be noise
- This is the most common two ways for people to include addtional artifacts in packages (we use files in our own init package)
- This is the most common two ways for people to include additional artifacts in packages (we use files in our own init package)
Cons:
- This is only a subset of what Zarf provides and someone could commit an artifact to a git repo for example

Expand Down
2 changes: 1 addition & 1 deletion docs/3-create-a-zarf-package/9-github-action.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ The [setup-zarf](https://github.com/defenseunicorns/setup-zarf) Github action is
```yaml
# .github/workflows/zarf-package-create.yml
jobs:
create_pacakge:
create_package:
runs-on: ubuntu-latest

name: Create my cool Zarf Package
Expand Down