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

feat: define CHANGELOG guidelines #20

Open
cmpadden opened this issue Oct 25, 2024 · 0 comments
Open

feat: define CHANGELOG guidelines #20

cmpadden opened this issue Oct 25, 2024 · 0 comments
Labels
good first issue Good for newcomers

Comments

@cmpadden
Copy link
Collaborator

Each integration can maintain its own CHANGELOG.

Define a set of guidelines, and outline in CONTRIBUTING.md in how we can maintain these entries.
@cmpadden cmpadden added the good first issue Good for newcomers label Oct 25, 2024
cmpadden pushed a commit that referenced this issue Dec 12, 2024
@christeefy
✨ Implement MessageWriter trait (#20)
dcf81cb 
* Post-release version update

* ✨ Implement simplified PipesMessageWriter trait

* 📝 Add docs

* 🔥 Simpify `DefaultWriter::Channel`

* 🐛 Fix error in example main.rs

* 📝 Update changelog

* Fix with Clippy lints

* Derive Clone for quicktype types

* Create constructor for PipesMessage

* ✅ Add unit tests

* ✚ Add `rstest` dev dep to test suite

* ✅ Add unit tests for message writer

And modify its return type to be an enum instead of Box

* fixup! Derive Clone for quicktype types
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cmpadden