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

build(fly): build before deploy #1015

Closed
wants to merge 2 commits into from

Conversation

@remix-cla-bot
Copy link
Contributor

remix-cla-bot bot commented Dec 12, 2021

Hi @CanRau,

Welcome, and thank you for contributing to Remix!

Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once.

You may review the CLA and sign it by adding your name to contributors.yml.

Once the CLA is signed, the CLA Signed label will be added to the pull request.

If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected].

Thanks!

- The Remix team

@remix-cla-bot
Copy link
Contributor

remix-cla-bot bot commented Dec 12, 2021

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳

Copy link
Member

@kentcdodds kentcdodds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR needs to be made to dev ratchet than the main branch. Not sure I think we should build before the deploy. What do we do in the other templates? Either way it should be the same with all the templates.

@CanRau
Copy link
Contributor Author

CanRau commented Dec 13, 2021

Yea sorry I was kinda distracted by making my first PR via gh-cli and forgot to add my reasoning

And for the branch, there isn't a way to move this right? So I close this one and make a new one on the other branch right?

@kentcdodds
Copy link
Member

That would be an easier way, yeah

@CanRau
Copy link
Contributor Author

CanRau commented Dec 13, 2021

Alright, before opening the new one I thought it might be better to check in, as we already have this discussion, sharing my thinking.

So, to me it was quite confusing, that running npm run deploy wouldn't update my website 😳 I know it's kinda my fault not properly checking what the npm scripts are doing, but there's also no mention of ever running npm run build in the Readme.

Therefore I propose either adding it to the readme or running it automatically before deploy.

Personally I prefer the latter as I don't have much reason to deploy without building, but there might be other preferences I guess.
As for what other templates are doing, the Workers one builds already before deploying and others don't require builds or deploys, as far as I can tell.

So closing this one, awaiting feedback on if and how to make a new PR to dev

@CanRau CanRau closed this Dec 13, 2021
@kentcdodds
Copy link
Member

Thanks for the feedback. I agree we should make a change. I just want to make sure we're the same in every template. Could you open an issue about it so it can be discussed and a decision can be made?

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

Successfully merging this pull request may close these issues.

2 participants