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

Set Up Now.sh Deploys + Travis Integration for Pattern Lab Node Repo #961

Closed
sghoweri opened this issue Oct 15, 2018 · 9 comments
Closed

Comments

@sghoweri
Copy link
Contributor

@bmuenzenmeyer I think we should move forward with setting up now.sh + Travis integration with the Pattern Lab Node repo -- basically having any passing Travis build automatically deploy a staged preview (of some generated starterkits?...) for testing, always up to date docs and demos, etc.

We're already doing something very similar with every PR and release in the Bolt Design System repo (including Github integration) so we have an easy to get to link we can share and reference for any upcoming changes upstream. As a bonus, this integration can also get used to deploy demos and docs to a live site / domain if configured with every new release.

I've already gone ahead and created a free OSS team for Pattern Lab -- identifying what makes the most sense to deploy + getting this integrated with the Github repo would probably be the next step...

@bradfrost
Copy link
Member

I'd welcome a nice visual/working preview of what the latest PL build looks like.

@stale
Copy link

stale bot commented Dec 14, 2018

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

@stale
Copy link

stale bot commented Dec 29, 2018

Issue closed after going stale. It can be re-opened if still relevant.

@stale stale bot closed this as completed Dec 29, 2018
@sghoweri sghoweri reopened this Dec 29, 2018
@stale
Copy link

stale bot commented Feb 27, 2019

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

@sghoweri
Copy link
Contributor Author

Bump! Still relevant + still needed . Don't want to see this closed out prematurely :)

@stale
Copy link

stale bot commented Apr 28, 2019

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

@sghoweri
Copy link
Contributor Author

Bump

@stale
Copy link

stale bot commented Jun 28, 2019

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

@stale
Copy link

stale bot commented Jul 28, 2019

Issue closed after going stale. It can be re-opened if still relevant.

@stale stale bot closed this as completed Jul 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants