Move from gitman to bigwigspackager
SamMousa opened this issue · 1 comments
You requested this in another issue. Let's discuss here.
What are the benefits you hope to gain?
Potential downsides I see:
- can't run packager locally
- harder to lock to specific version of a dependency
So what's the underlying requirements that are not currently being fulfilled?
My end-goal here is to simplify the CI flow since now we have way more
stages than I feel (#feelscrafts) is needed. If we could have one script to
cover both locally and in CI (so running packager to drop build locally)
would be nice, but if thats not possible I'm open to any other
simplification proposals
pt., 14 paź 2022 o 09:56 Sam ***@***.***> napisał(a):
… You requested this in another issue. Let's discuss here.
What are the benefits you hope to gain?
Potential downsides I see:
- can't run packager locally
- harder to lock to specific version of a dependency
So what's the underlying requirements that are not currently being
fulfilled?
—
Reply to this email directly, view it on GitHub
<#389>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKIXVTNHZX2P55A2DF4DAX3WDEG2VANCNFSM6AAAAAARE7OUME>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
*Z wyrazami szacunku*
*Dolecki Szymon*