Repository navigation
Setup GitHub Release for Production Deployments #29
Description
Activity
Additional Note: if/when we do this, we will want to un-skip the test in homePage.test.js checking for the version link!
probably that should also address the issue of incorrect
describeon the mainpage:
or do you just need tags?
probably that should also address the issue of incorrect
describeon the mainpage:or do you just need tags?
My understanding is that if we used tags then the version would show up in more user-friendly way (i.e. version v0.13.1) , like on https://dandiarchive.org
So I think yes using releases would also achieve this
I'd like to suggest that we revert back to using GitHub Releases to start the production deploy and have a single default
prod(or differently named) branch that sandbox (and production) deploys from.Pros:
For reference, our current workflow is as follows:
<issue-branch><issue-branch>intoapl-setupa.
apl-setupbranch is deployed to the Sandbox App https://apl-setup--ember-dandi-archive.netlify.app/apl-setuptoproda.
prodbranch is deployed to the Production App https://dandi.emberarchive.orgWelcome additional thoughts & pros/cons!