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 Preview URL on a PR #23

Open
edmundmiller opened this issue Aug 14, 2023 · 6 comments
Open

Build Preview URL on a PR #23

edmundmiller opened this issue Aug 14, 2023 · 6 comments
Assignees

Comments

@edmundmiller
Copy link
Collaborator

Follow up to #22

@edmundmiller edmundmiller self-assigned this Aug 14, 2023
@edmundmiller edmundmiller changed the title Build Preview URL on a PR from a fork Build Preview URL on a PR Aug 14, 2023
@edmundmiller
Copy link
Collaborator Author

#24

@kescobo
Copy link
Member

kescobo commented Aug 14, 2023

Should we revert the original build workflow until this is resolved?

For the record, I'm fine with you merging stuff to master on your own to test this stuff, as long as you're able to revert if a build goes awry. I don't think anything here is so critical that a few minutes of downtime is a problem, just don't kick off a build and go to bed :-D

@edmundmiller
Copy link
Collaborator Author

Roger that!

I don't think it needs reverting, I think it's still deploying on master fine, so there's no regression?

@kescobo
Copy link
Member

kescobo commented Aug 28, 2023

Well, for folks that have write access and make a PR from a branch in this repo (as opposed to a fork), the build preview was working. It's not a huge deal (and I'm having a baby in 5 days, so not like I'm gonna be doing much in the next few weeks / months), but if other folks want it - it's something to be considered.

@edmundmiller
Copy link
Collaborator Author

Ah gotcha, so this was working previously but not now? Going off this example: #24

Congrats! Take care and enjoy your time!

@kescobo
Copy link
Member

kescobo commented Aug 30, 2023

Yeah, that PR was after this change. See here #17 (comment) - it was a brief, glorious moment where it was working 😆

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