-
Notifications
You must be signed in to change notification settings - Fork 313
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
Issue #299: Types provided for effects, with Go Package being the ref… #635
Issue #299: Types provided for effects, with Go Package being the ref… #635
Conversation
…the reference, in addition to moving Asset and Offer Types to their own files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this work; it's a great contribution! I just noticed some minor typos in the type definitions; please give those a look.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, looks great now! As a final touch, can you add a note (under the Unreleased heading) to the CHANGELOG summarizing this? Please follow the format of the other entries.
…nes + removed a type that was a duplicate + CCHANGELOG entry
Last hurdle, @RabeaWahab, as you can see in the approval checklist: all of your commits need to be GPG signed! It's a bit of effort to set up, but our repository unconditionally requires that commits be signed. Once you've configured your keys, since you already have unsigned commits, you will need to rebase & squash them all into a single, signed commit, e.g.
The first line should be the commit right before your PR's commits. Edit the lines to say
to sign it. |
Actually, I'm going to go ahead and merge this. Be sure to set up signed commits for the future, though, this project and many others impose these kinds of requirements to trace changes and provide author authenticity. Thank you again for your contribution! This will be part of the next release. 👍 |
Thank you @Shaptic , I will have it ready for the next PR. 🙏 again I appreciate the quick feedback from you and @paulbellamy |
Any feedback is really appreciated.
Closes #299.