Reorganize reusable workflows #147
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We want to maintain only one copy of each reusable workflow between libbpf/ci and kernel-patches/vmtests [1]. To achieve that, libbpf/ci is going to be the source of truth for them, and kernel-patches/vmtest main workflow will be calling libbpf/ci. This change reorganizes files to make it clear which workflows are reusable, and which are repository-specific. I suggest the following convention: * `.github` contains workflows local to the owner repository * `workflows` contains reusable workflows, intened for external use [1]: https://github.com/kernel-patches/vmtest/tree/master/.github
|
As it turns out, we can't do that because reasons. Not only can't we move to repo root, we also can't use a subdirectory in
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want to maintain only one copy of each reusable workflow between libbpf/ci and kernel-patches/vmtests 1. To achieve that, libbpf/ci is going to be the source of truth for them, and kernel-patches/vmtest main workflow will be calling libbpf/ci.
This change reorganizes files to make it clear which workflows are reusable, and which are repository-specific. I suggest the following convention:
.githubcontains workflows local to the owner repositoryworkflowscontains reusable workflows, intened for external use