You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't see why the production part isn't the same that preview part.
The first time you arrive to this page, you could think that the preview part is the list of all builds, included the production. And the production part is just a summary of the last production build.
Plus I don't get it how to restart a production build when I've got an error (like an API error I fixed and I want to restart the build).
The text was updated successfully, but these errors were encountered:
There is an option to re-deploy if you go to the a deployment's Overview →
I am not sure if I understand your issue with the UI — we explicitly differentiate the Production and Preview deployments on this view. If you go to your list of Deployments, it will show both Production and Preview deployments.
The thing is I've got this for the production mode:
And sometimes I don't want/need to send a new commit, I just need to fix my API and rebuilld the production.
For the Production and Preview parts, it's just that the design is really different where - to me - it could be exactly displayed the same way (I only speak about the design, not the fact that it's separated).
To be honest I'd like to gave like the 5 last builds for my production for example.
Hello,
To me, this UI isn't so clear.
I don't see why the
production
part isn't the same thatpreview part
.The first time you arrive to this page, you could think that the
preview
part is the list of all builds, included the production. And theproduction
part is just a summary of the last production build.Plus I don't get it how to restart a production build when I've got an error (like an API error I fixed and I want to restart the build).
The text was updated successfully, but these errors were encountered: