This repository was archived by the owner on Oct 13, 2024. It is now read-only.
update docker workflow - #190
Merged
Merged
Conversation
ReenigneArcher
force-pushed
the
update-docker-workflow
branch
6 times, most recently
from
January 14, 2023 15:12
7da3f94 to
b62c9cd
Compare
30 tasks
ReenigneArcher
force-pushed
the
update-docker-workflow
branch
from
January 14, 2023 21:22
b62c9cd to
771ff4c
Compare
ReenigneArcher
force-pushed
the
update-docker-workflow
branch
from
January 15, 2023 00:53
771ff4c to
4cceb51
Compare
11 tasks
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Update docker workflow, based on changes from LizardByte/Sunshine#714. It is intended that this workflow file works universally for all our docker projects.
Todo:
.githubrepo.Screenshot
Issues Fixed or Closed
Type of Change
.github/...)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.