-
Notifications
You must be signed in to change notification settings - Fork 14
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: Use shared GitHub Actions #247
Merged
kyma-bot
merged 19 commits into
kyma-project:main
from
c-pius:chore/shared-github-actions
Apr 17, 2024
Merged
chore: Use shared GitHub Actions #247
kyma-bot
merged 19 commits into
kyma-project:main
from
c-pius:chore/shared-github-actions
Apr 17, 2024
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
kyma-bot
added
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
cla: yes
Indicates the PR's author has signed the CLA.
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
labels
Apr 5, 2024
c-pius
force-pushed
the
chore/shared-github-actions
branch
2 times, most recently
from
April 5, 2024 12:15
53096c6
to
0233f64
Compare
kyma-bot
added
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
and removed
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
labels
Apr 16, 2024
c-pius
force-pushed
the
chore/shared-github-actions
branch
from
April 16, 2024 11:18
58bb704
to
4272a59
Compare
c-pius
changed the title
wip: Introduce shared GitHub Actions
chore: Introduce shared GitHub Actions
Apr 16, 2024
kyma-bot
removed
the
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
label
Apr 16, 2024
c-pius
force-pushed
the
chore/shared-github-actions
branch
from
April 16, 2024 11:25
23bd44e
to
bb080d2
Compare
kyma-bot
added
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
and removed
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
labels
Apr 16, 2024
c-pius
changed the title
chore: Introduce shared GitHub Actions
chore: Use shared GitHub Actions
Apr 16, 2024
kyma-bot
added
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
and removed
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
labels
Apr 16, 2024
c-pius
commented
Apr 16, 2024
kyma-bot
added
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
and removed
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
labels
Apr 17, 2024
nesmabadr
approved these changes
Apr 17, 2024
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.
Description
Changes proposed in this pull request:
Related issue(s)
Comments
To ease the review allowing to compare the new workflow runs against the old ones, the oldtest-e2e.yaml
workflow is still there unchanged and the new workflow is intest-e2e-junk.yaml
. Once the changes are good to go, the old file will be updated with the new workflow and the separate junk file will be deleted.When reviewing, it is probably best to start fromtest-e2e-junk.yaml
and from there look into the used helper actions.