Skip to content

Conversation

@DmitrySharabin
Copy link
Collaborator

@DmitrySharabin DmitrySharabin commented Nov 5, 2025

This repo is a submodule of the website repo, so we need to deploy it on every change to this repo.

Let's consider this action as an experiment. In the event of success, we should add the corresponding secret to the organization itself and copy and paste this workflow to every project repository. Probably, create a project template repo with this workflow already in place? Is it possible?

Org secrets: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets#creating-secrets-for-an-organization

This repo is a submodule of the website repo, so we need to deploy it on every change to this repo.
@LeaVerou
Copy link
Member

LeaVerou commented Nov 5, 2025

Doesn't GitHub have a webhooks feature where you can paste a URL to trigger whenever there's a push? Netlify does provide such URLs. It seems like it may be simpler than a GitHub action? OTOH the GH Action makes it clear what's happening to anyone looking at the repo. No strong opinion 🤔

@DmitrySharabin
Copy link
Collaborator Author

Doesn't GitHub have a webhooks feature where you can paste a URL to trigger whenever there's a push? Netlify does provide such URLs. It seems like it may be simpler than a GitHub action?

Oh, I didn't know about GH webhooks (TIL). And yes, those are much simpler and a better approach. I'd use org webhooks in that case.

OTOH the GH Action makes it clear what's happening to anyone looking at the repo. No strong opinion 🤔

From my perspective, people working on the project don't have to think about anything website-related. One important thing is that when they push, their change will be immediately (sort of) available on the website.

I'm gonna close this PR and remove the repo secret. Thanks for the idea!

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

Successfully merging this pull request may close these issues.

3 participants