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

[TECH] Déployer Storybook à chaque release #583

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

yannbertrand
Copy link
Member

🎄 Problème

Notre Storybook ui.pix.fr ne se déploie plus automatiquement depuis la v44.0.0 (voir le changelog).

🎁 Proposition

Ne plus contraindre le déploiement (avec un if qui ne passe jamais ^^").

🌟 Remarques

RAS

🎅 Pour tester

Je ne sais pas.

@yannbertrand yannbertrand added 👀 Tech Review Needed cross-team Toutes les équipes de dev labels Mar 22, 2024
@yannbertrand yannbertrand self-assigned this Mar 22, 2024
@pix-bot-github
Copy link

Une fois l'application déployée, elle sera accessible à cette adresse https://ui-pr583.review.pix.fr
Les variables d'environnement seront accessibles sur scalingo https://dashboard.scalingo.com/apps/osc-fr1/pix-ui-review-pr583/environment

@pix-service-auto-merge pix-service-auto-merge force-pushed the fix-storybook-deployment-release branch from 1bd51e9 to 68c5184 Compare March 22, 2024 10:38
@pix-service-auto-merge pix-service-auto-merge merged commit d2504b7 into dev Mar 22, 2024
3 of 6 checks passed
@pix-service-auto-merge pix-service-auto-merge deleted the fix-storybook-deployment-release branch March 22, 2024 10:42
pix-service-auto-merge pushed a commit that referenced this pull request Mar 22, 2024
## [45.0.1](v45.0.0...v45.0.1) (2024-03-22)

### 🏗️ Tech

- [#583](#583) Déployer Storybook à chaque release
@pix-service-auto-merge
Copy link
Contributor

🎉 This PR is included in version 45.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

4 participants