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

Remove gh-pages deploy in favor of netlify #4128

Merged
merged 3 commits into from
Sep 7, 2018

Conversation

shilman
Copy link
Member

@shilman shilman commented Sep 6, 2018

Issue: #4126

What I did

  • Remove gh-pages deploy from circle config
  • Keep the docs build just so we can be sure that it builds
  • Keep the deploy step as a placeholder

Now the gh-pages branch will go out of date (and we should probably remove it once we are fully onto netlify), and storybook.js.org points to the netlify instance rather than to storybooks.github.io/storybook (See js-org/js.org#2304)

How to test

Not really testable until we merge this into a tag vX.Y.Z commit. But I've been messing around with this for an hour or so, and am confident it's safe.

Keep the deploy step as a placeholder
@shilman shilman added the maintenance User-facing maintenance tasks label Sep 6, 2018
@shilman shilman requested a review from ndelangen as a code owner September 6, 2018 00:35
@codecov
Copy link

codecov bot commented Sep 6, 2018

Codecov Report

❗ No coverage uploaded for pull request base (master@013822a). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #4128   +/-   ##
=========================================
  Coverage          ?   40.59%           
=========================================
  Files             ?      483           
  Lines             ?     5747           
  Branches          ?      770           
=========================================
  Hits              ?     2333           
  Misses            ?     3042           
  Partials          ?      372

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 013822a...476a4e3. Read the comment docs.

git config --global user.email "gh-pages@localhost"
git config --global user.name "npm gh-pages"
yarn deploy:ci
echo "Nothing to deploy"
Copy link
Member

Choose a reason for hiding this comment

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

You can remove the whole job.

Copy link
Member

@ndelangen ndelangen left a comment

Choose a reason for hiding this comment

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

please remove the whole job from config

Copy link
Member

@pksunkara pksunkara left a comment

Choose a reason for hiding this comment

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

@pksunkara
Copy link
Member

@shilman Before merging this PR, could you please address this? #4126 (comment). We need to figure out what process we are going to follow.

@pksunkara
Copy link
Member

I actually realized that the current deploy job is broken anyway because of circleci tag filter rule. So, I am merging this.

@pksunkara pksunkara merged commit 0d4a63e into master Sep 7, 2018
@pksunkara pksunkara deleted the shilman/4126-remove-gh-pages-deploy branch September 7, 2018 18:48
@Hypnosphi Hypnosphi added the patch:yes Bugfix & documentation PR that need to be picked to main branch label Sep 30, 2018
@shilman shilman added the patch:done Patch/release PRs already cherry-picked to main/release branch label Oct 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance User-facing maintenance tasks patch:done Patch/release PRs already cherry-picked to main/release branch patch:yes Bugfix & documentation PR that need to be picked to main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants