-
Notifications
You must be signed in to change notification settings - Fork 0
fix bug related to missing contact_method information in some cases #27
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
Conversation
- Updated aca_entities gem version - Updated preview payload to include health and dental enrollments - Fixed bug related to missing contact_method information in some cases - Updated verabiage for Cub Care in application settings
markgoho
left a comment
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.
please update PR title to be less generic
|
@markgoho like ? |
|
@Battula this is up to you as the developer to describe your changes in a way that conveys meaning and summarizes what's changing about the code what you've written amounts to "made changes" -- yeah, okay, that's what a PR does, but what changes are you making? If you're finding it difficult to summarize the changes, it's possible you've put too much in the PR and it needs to be broken out in to separate changes, each able to be independently reviewed |
|
@Battula I'm not finding it difficult to understand the changes, I'm finding it difficult to see how "made changes" properly summarizes a number of distinct changes options:
|
|
@markgoho I can't summarize all the changes in the PR title, so I came up with a generic title and summarized the changes in the comment section. |
|
@Battula please submit PRs for each of these:
|
|
@markgoho May I please know what's wrong with this PR ? |
|
@Battula this PR clearly combines 4 different changes to the codebase that each need their own PR here are the PRs I expect to see:
|
|
All the changes are related to FRE notice, and I don't see why they can't be on a single pull request. @markgoho |
|
@markgoho Please don't close this PR, we need this to be merged to trunk. Thank you! |
ME-180463890