use generic worfklow for build#181
Open
jonenst wants to merge 1 commit into
Open
Conversation
Member
|
I don't see Edit: found it in branch buildfrontendlib which have no PR yet. |
jonenst
force-pushed
the
buildcommonworkflow
branch
from
March 26, 2025 10:11
5b42cac to
4264999
Compare
Collaborator
Author
|
852670523f7f merged in main in github-ci |
jonenst
force-pushed
the
buildcommonworkflow
branch
from
March 26, 2025 15:59
4264999 to
3d65680
Compare
jonenst
force-pushed
the
buildcommonworkflow
branch
from
March 26, 2025 16:01
3d65680 to
14fd196
Compare
Signed-off-by: HARPER Jon <jon.harper87@gmail.com>
jonenst
force-pushed
the
buildcommonworkflow
branch
from
March 27, 2025 08:02
14fd196 to
2bccf23
Compare
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
NO
What kind of change does this PR introduce?
chore
What is the current behavior?
duplicated build workflow
What is the new behavior (if this is a feature change)?
using generic build workflow
Does this PR introduce a breaking change or deprecate an API?
Other information:
Adds broadcast-event