Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate Deployment on Main Branch Merge #13

Open
tekrajchhetri opened this issue Nov 22, 2024 · 4 comments
Open

Automate Deployment on Main Branch Merge #13

tekrajchhetri opened this issue Nov 22, 2024 · 4 comments
Assignees

Comments

@tekrajchhetri
Copy link
Collaborator

tekrajchhetri commented Nov 22, 2024

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
Copy link
Member

kabilar commented Dec 4, 2024

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
Copy link
Collaborator Author

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

@kabilar
Copy link
Member

kabilar commented Dec 4, 2024

@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
Copy link
Member

kabilar commented Dec 4, 2024

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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants