try to build release plume&plm on ci #528
Nav izskatītāju
Iezīmes
Nav iezīmju
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Nav atskaites punkta
Nav projektu
Nav atbildīgo
2 dalībnieki
Paziņojumi
Izpildes datums
Nav uzstādīts izpildes datums.
Atkarības
Nav atkarību.
Atsauce: Plume/Plume#528
Notiek ielāde…
Pievienot tabulu
Atsaukties jaunā pieteikumā
Nav sniegts apraksts.
Izdzēst zaru "artifact"
Zara izdzēšana ir neatgriezeniska. Kaut arī izdzēstais zars neilgu laiku var turpināt pastāvēt, pirms tas patiešām tiek noņemts, to vairumā gadījumu NEVAR atsaukt. Turpināt?
ref Plume-org/docs#27
I should archive the artifacts before uploading
👍
Codecov Report
Would it be possible to bundle the diesel CLI too, please?
And also the migration files?
Shoulf I include both migrations, only the one of interest as
migrations/$db_name
or only the one of interest asmigrations/
(maybe not the latest as it will not be compatible with our documentation?)I'm not sure i've asked this before, but, how hard would it be to support both databases? at the same time?
I see 2 ways of doing so :
Box<Connection>
everywhereBut I don't know how any of those would play with r2d2 (the connection manager)
Couldn't it be possible to make all our models generic over the connection type that is used? (but that's probably more work than what you proposed)
And for the migrations, the best is to have only the relevant one in
migrations/$db
to make the archive smaller and keep compatibility with our current docs.Thank you!
(I wanted to approve this PR)