We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We want to allow people to create workflows with the same name in the scope of the projects.
So for example we could have project-1/build-and-test or project-2/build-and-test
note: This might potentially mean a breaking change w.r.t initializing workflows.
### Phase 0 - [x] Rename project by product - [x] Release CLI with –project support - [x] Double-check that project-name is also DNS-1131 compatible - [x] migrate workflow create --product flag - [x] migrate --product in att init - [x] update labs https://github.com/chainloop-dev/labs/pull/34 - [x] migrate gitlab - [x] internal repos - [ ] https://github.com/chainloop-dev/chainloop/issues/1390
### Phase 1 - [x] migrate dagger - [x] Change DB constraint - [x] Upgrade Dagger module - [x] Update CLI accordingly to start attestation with the project - [x] cleanup and enforce constraint - [x] remove dagger optional project - [x] remove optional project in CLI
The text was updated successfully, but these errors were encountered:
migmartri
Successfully merging a pull request may close this issue.
We want to allow people to create workflows with the same name in the scope of the projects.
So for example we could have project-1/build-and-test or project-2/build-and-test
note: This might potentially mean a breaking change w.r.t initializing workflows.
The text was updated successfully, but these errors were encountered: