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

chore: move to new witness repo #493

Closed

Conversation

mikhailswift
Copy link
Contributor

@mikhailswift mikhailswift commented May 26, 2022

We've split out the library code of witness into it's own repository,
separate from the CLI code. No other changes and this just switches
zarf to point to the new repository.

Description

Related Issue

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist before merging

  • Tests have been added/updated as necessary (add the needs-tests label)
  • Documentation has been updated as necessary (add the needs-docs label)
  • An ADR has been written as necessary (add the needs-adr label) [ 1 2 3 ]
  • (Optional) Changes have been linted locally with golangci-lint. (NOTE: We haven't turned on lint checks in the pipeline yet so linting may be hard if it shows a lot of lint errors in places that weren't touched by changes. Thus, linting is optional right now.)

We've split out the library code of witness into it's own repository,
separate from the CLI code.  No other changes and this just switches
zarf to point to the new repository.
@jeff-mccoy
Copy link
Contributor

Rolling this into #495, thanks.

@jeff-mccoy jeff-mccoy closed this May 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants