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

Basic implementation #1

Merged
merged 69 commits into from
Mar 13, 2023
Merged

Basic implementation #1

merged 69 commits into from
Mar 13, 2023

Conversation

strieflin
Copy link
Member

This is an initial, still sketchy, implementation of Klyshko based in Golang made available to allow for early feedback. No tests at all yet.

@strieflin strieflin added the kind/feature Categorizes issue or PR as related to a new feature. label May 20, 2022
Copy link

@kindlich kindlich left a comment

Choose a reason for hiding this comment

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

I didn't check the license files and files that looked like they were auto-generated, I'll trust you there 😉

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
hack/deploy.sh Show resolved Hide resolved
hack/deploy.sh Outdated Show resolved Hide resolved
hack/deploy.sh Outdated Show resolved Hide resolved
klyshko-provisioner/README.md Show resolved Hide resolved
klyshko-provisioner/hack/deploy.sh Show resolved Hide resolved
klyshko-provisioner/kii-provisioner-run.sh Outdated Show resolved Hide resolved
klyshko-provisioner/kii-provisioner-run.sh Show resolved Hide resolved
klyshko-provisioner/kii-provisioner-run.sh Show resolved Hide resolved
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
Signed-off-by: Sven Trieflinger <[email protected]>
@strieflin
Copy link
Member Author

Fixes #5.

@strieflin strieflin mentioned this pull request Dec 21, 2022
Copy link
Member

@sbckr sbckr left a comment

Choose a reason for hiding this comment

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

I would expect the basic implementation to also provide a workflow configuration to create github releases, e.g., as provided with ephemeral/.github/workflows/publish-and-release.yaml, as well as an auto labeler and stale issue cleanup configuration.
❗ Especially important is the part which collects and bundles the 3rd-party license information.

Please also note the comments in the files.

README.md Outdated Show resolved Hide resolved
key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
restore-keys: |
${{ runner.os }}-go-
- name: Build and Test
Copy link
Member

@sbckr sbckr Mar 3, 2023

Choose a reason for hiding this comment

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

I'd expect test and release to be defined in separate workflows as tests are supposed to be run with each PR created, but release only for commits on the master branch. (see ephemeral as reference)

Copy link
Member Author

@strieflin strieflin Mar 11, 2023

Choose a reason for hiding this comment

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

We will pilot the use of release-please in Klyshko. Build/test and publish logic has been separated as part of this. This also computes the right labels and release names automatically.

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
@strieflin
Copy link
Member Author

Workflows for auto labelling and stale issue handling have been added.

@strieflin strieflin force-pushed the basic-implementation branch 3 times, most recently from 3021818 to aeeb0f3 Compare March 7, 2023 15:32
Signed-off-by: Sven Trieflinger <[email protected]>
@strieflin
Copy link
Member Author

Workflows for auto labelling and stale issue handling have been added.

These have been removed again as they are available in master already.

@strieflin strieflin requested a review from sbckr March 11, 2023 09:25
@strieflin strieflin marked this pull request as ready for review March 11, 2023 09:26
Copy link
Member

@sbckr sbckr left a comment

Choose a reason for hiding this comment

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

LGTM

@sbckr sbckr merged commit b4da582 into master Mar 13, 2023
@sbckr sbckr deleted the basic-implementation branch March 13, 2023 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants