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

Feature: convention for issue titles to filter Palette changelog #241

Open
kierangillen opened this issue Jan 30, 2019 · 4 comments
Open

Comments

@kierangillen
Copy link
Contributor

kierangillen commented Jan 30, 2019

  • We discussed the possibility for a new convention for issue titles for new and updated components in Palette. This convention could allow for filtering changelog updates to specific components for a changelog tab.
@kierangillen kierangillen changed the title Convention for issue titles to filter Palette changelog Feature: Convention for issue titles to filter Palette changelog Jan 30, 2019
@kierangillen kierangillen changed the title Feature: Convention for issue titles to filter Palette changelog Feature: convention for issue titles to filter Palette changelog Jan 30, 2019
@alloy
Copy link
Contributor

alloy commented Jan 31, 2019

[ComponentName] Description of the change. ?

@kierangillen
Copy link
Contributor Author

@alloy I think that makes sense, @damassi @zephraph what do ya'll think?

@damassi
Copy link
Member

damassi commented Jan 31, 2019

I know @zephraph mentioned yesterday in our meeting that labels are filterable (but I have no preference either way).

@zephraph
Copy link
Contributor

zephraph commented Feb 6, 2019

Yeah, a few thoughts here.

Auto release generates a changelog (and releases) based on release labels of PRs. Ultimately the PRs are what drives changes. We can customize the labels, changelog titles, and release process as much as we need.

For issues, if it's a categorical thing (i.e. feature request, proposal, RFC, etc) then I think it should be a label because as @damassi said we can filter on those. If it's a unique thing (i.e. a component name) then it needs to go in the title.

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

4 participants