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.

Sign up for GitHub

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

Jump to bottom

Send changelogs #797

Open
wheresrhys opened this issue Aug 24, 2022 · 1 comment
Open

Send changelogs #797

wheresrhys opened this issue Aug 24, 2022 · 1 comment
Assignees
@notlee
Labels
next planning Used to mark an issue to discuss in Origami's next planning session
Projects
Origami ✨

Comments

@wheresrhys
Copy link
Contributor

I discussed this with @chee ages ago but didn't really arrive at any conclusions. The code origami being squatted by the origami website was a bit of a blocker to progressing, but that is now resolved.

So the ideal is that

  1. when the app or storybook is released a change log is sent for their respective system codes (though I note that storybook doesn't have a system code yet 🙈 )
  2. When components/tools are released then a changelog is sent with the code origami*, ideally sending details of which packages in the extraProperties field

*because change-api does not yet support sending changelogs for packages
@origamiserviceuser origamiserviceuser added this to Backlog in Origami ✨ Aug 24, 2022
@chee
Copy link
Member

chee commented Aug 26, 2022

the storybook probably comes under the origami-website system code? it's built to static files placed into the website's storybook/ directory

@KamranMuniree KamranMuniree added the next planning Used to mark an issue to discuss in Origami's next planning session label Sep 6, 2022
@KamranMuniree KamranMuniree moved this from Backlog to To Do in Origami ✨ Oct 3, 2022
@KamranMuniree KamranMuniree removed the next planning Used to mark an issue to discuss in Origami's next planning session label Oct 3, 2022
@KamranMuniree KamranMuniree added the next planning Used to mark an issue to discuss in Origami's next planning session label Oct 25, 2022
@KamranMuniree KamranMuniree moved this from To Do to Backlog in Origami ✨ Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@notlee notlee

Labels
next planning Used to mark an issue to discuss in Origami's next planning session
Projects
Origami ✨
  
Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@chee @wheresrhys @notlee @KamranMuniree