Automate Deployment on Main Branch Merge

[tekrajchhetri]

Summary:

Implement a GitHub Action to automate the deployment process whenever changes are merged into the main branch. This feature will streamline the deployment workflow and reduce manual intervention.

Details:

• Requested by: @kabilar
• Purpose: Ensure that every merge to the main branch triggers an automated deployment process to maintain consistency and reduce deployment delays.

@kabilar will show how the automated deployment are used in other projects.

[kabilar]

Thanks @tekrajchhetri.

DANDI and LINC use Netlify to manage the front-end deployment to production and to provide previews upon creating pull requests.

The netlify.toml file configures Netlify, and Netlify watches the repo to create automated previews and deployments. You can find more details on how to configure Netlify in this pull request - dandi/dandi-docs#104.

[tekrajchhetri]

@kabilar Quick question, what will happen to the preview site upon pull request merge?

[kabilar]

@kabilar Quick question, what will happen to the preview site upon pull request merge?

Looks like deploy previews live forever - https://answers.netlify.com/t/does-each-deploy-preview-stay-available-forever/12601

[kabilar]

Also, please note that the Netlify Pro Plan is needed to create DNS records for subdomains. However, if your project qualifies, you can apply for the sponsored open-source plan - https://www.netlify.com/legal/open-source-policy/